Label switching path establishment method, data forwarding method, and device

ABSTRACT

Embodiments of the present invention provide a label switching path establishment method, a data forwarding method, and a device. The establishment method includes: determining, by a first service controller, each hop on an LSP from a preset ingress to a preset egress, allocating, from first label space information of each hop, a label to each hop, determining incoming and outgoing information of each hop according to topology information of each hop, generating forwarding data of each hop, and sending the forwarding data of each hop to a node device corresponding to each hop to complete establishment of the LSP. A technical solution of the present invention can alleviate burden of a node device in an MPLS network and increase the number of LSPs that the node device is capable of supporting.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2012/078704, filed on Jul. 16, 2012, which is hereby incorporatedby reference in its entirety.

TECHNICAL FIELD

This application relates to communications technologies, and inparticular, to a label switching path (LSP) establishment method, a dataforwarding method, and a device.

BACKGROUND

In an existing Multiprotocol Label Switching (MPLS) domain, the ResourceReservation Protocol-Traffic Engineering (RSVP-TE) signaling protocol isgenerally used to establish an LSP.

In an MPLS network, each node is configured with the RSVP-TE protocoland is configured with an interface with a need to run the RSVP-TEprotocol to run the RSVP-TE protocol. Between two adjacent nodes in theMPLS network, the RSVP-TE protocol maintains a peer relationship betweenthe nodes by using a Hello packet. When an LSP is established, theRSVP-TE protocol sends, from an ingress, a path message downstream andhop by hop and then sends, from an egress, a reservation (Resv) messageto the ingress. When receiving the Resv message, each hop on a linkreserves a bandwidth resource for the LSP, allocates a label, and sendsthe label to an upstream node by using the Resv message. After the Resvmessage arrives at the ingress, the RSVP-TE protocol regards that theentire LSP is successfully established.

By default, the RSVP-TE protocol sends a Hello message periodicallyevery 3 s, sends the Path message to the downstream node periodicallyevery 3 s, and sends the Resv message to the upstream node. It isevident that, in order to maintain link and LSP status information, theRSVP-TE protocol needs to send lots of soft state packets such as Hello,Path, and Resv, which causes heavy load to a node and reduces the numberof RSVP-TE LSPs that the node is capable of supporting.

SUMMARY

This application provides a label switching path establishment method, adata forwarding method, and a device, so as to alleviate burden of aforwarding device in an MPLS network and increase the number of LSPsthat the forwarding device is capable of supporting.

According to one aspect, this application provides a label switchingpath establishment method, including:

determining, by a first service controller, each hop on an LSP from apreset ingress to a preset egress; and

allocating, by the first service controller from first label spaceinformation of each hop, a label to each hop, determining incoming andoutgoing interface information of each hop according to topologyinformation of each hop, generating forwarding data of each hop, andsending the forwarding data of each hop to a node device correspondingto each hop to complete establishment of the LSP.

In an optional implementation manner of the foregoing method, thedetermining, by a first service controller, each hop on an LSP from apreset ingress to a preset egress includes: determining, by the firstservice controller, each hop on a first LSP and a second LSP that have aprimary/standby protection relationship and are from the preset ingressto the preset egress.

In an optional implementation manner of the foregoing method, theallocating, by the first service controller from first label spaceinformation of each hop, a label to each hop, determining incoming andoutgoing interface information of each hop according to topologyinformation of each hop, generating forwarding data of each hop, andsending the forwarding data of each hop to a node device correspondingto each hop to complete establishment of the LSP includes: allocating,by the first service controller from first label space information ofeach hop on the first LSP, a label to each hop on the first LSP,determining incoming and outgoing interface information of each hop onthe first LSP according to topology information of each hop on the firstLSP, generating forwarding data of each hop on the first LSP, and thensending the forwarding data of each hop on the first LSP to a nodedevice corresponding to each hop on the first LSP to completeestablishment of the first LSP.

In an optional implementation manner of the foregoing method, the methodfurther includes: sending, by the first service controller, identifierinformation of each hop on the second LSP to a second servicecontroller, so that the second service controller allocates, from secondlabel space information of each hop on the second LSP, a label to eachhop on the second LSP, determines incoming and outgoing interfaceinformation of each hop on the second LSP according to topologyinformation of each hop on the second LSP, generates forwarding data ofeach hop on the second LSP, and then sends the forwarding data of eachhop on the second LSP to a node device corresponding to each hop on thesecond LSP to complete establishment of the second LSP.

In an optional implementation manner of the foregoing method, the firstservice controller and the second service controller are connectedthrough another network except a first network to which the firstservice controller and the second service controller belong;

the determining, by the first service controller, each hop on a firstLSP from the preset ingress to the preset egress includes: determining,by the first service controller, each hop that is located in the firstnetwork on the first LSP from the preset ingress to the preset egress,where the first LSP passes through the other network; and

accordingly, the allocating, by the first service controller from firstlabel space information of each hop on the first LSP, a label to eachhop on the first LSP, determining incoming and outgoing interfaceinformation of each hop on the first LSP according to the topologyinformation of each hop on the first LSP, and generating forwarding dataof each hop on the first LSP includes:

triggering, by the first service controller, establishment of a thirdLSP, where the third LSP is an LSP that uses the first servicecontroller as an ingress, uses the second service controller as anegress, and passes through the other network; and

allocating, by the first service controller from first label spaceinformation of each hop that is located in the first network on thefirst LSP, a label to each hop that is located in the first network onthe first LSP; determining incoming and outgoing interface informationof each hop that is located in the first network on the first LSPaccording to topology information of each hop that is located in thefirst network on the first LSP; stitching the first LSP and the thirdLSP; and generating forwarding data of each hop that is located in thefirst network and each hop that is located in the other network on thefirst LSP.

In an optional implementation manner of the foregoing method, thestitching, by the first service controller, the first LSP and the thirdLSP includes:

allocating, by the first service controller, an incoming label to thefirst service controller on the third LSP, where the incoming label isan outgoing label of a previous hop of the first service controller onthe first LSP; and

allocating, by the first service controller, an outgoing label to thesecond service controller on the third LSP, where the outgoing label isan incoming label of a next hop of the second service controller on thefirst LSP, where

each hop on the third LSP except the first service controller and thesecond service controller constitutes each hop that is located in theother network on the first LSP.

In an optional implementation manner of the foregoing method, the firstservice controller and the second service controller are connectedthrough another network except a first network to which the firstservice controller and the second service controller belong;

the determining, by the first service controller, each hop on a secondLSP from the preset ingress to the preset egress includes: determining,by the first service controller, each hop that is located in the firstnetwork on the second LSP from the preset ingress to the preset egress,where the second LSP passes through the other network; and

accordingly, the sending, by the first service controller, identifierinformation of each hop on the second LSP to a second service controllerincludes:

triggering, by the first service controller, establishment of a fourthLSP, where the fourth LSP is an LSP that uses the first servicecontroller as an ingress, uses the second service controller as anegress, and passes through the other network; and

sending, by the first service controller, a stitching and bindingrelationship between the second LSP and the fourth LSP, identifierinformation of each hop that is located in the first network on thesecond LSP, and identifier information of the ingress of the fourth LSPto the second service controller.

In an optional implementation manner of the foregoing method, theallocating, by the first service controller from first label spaceinformation of each hop, a label to each hop, determining incoming andoutgoing interface information of each hop according to topologyinformation of each hop, generating forwarding data of each hop, andsending the forwarding data of each hop to a node device correspondingto each hop to complete establishment of the LSP includes: allocating,by the first service controller from first label space information ofeach hop on the first LSP, a label to each hop on the first LSP,determining incoming and outgoing interface information of each hop onthe first LSP according to topology information of each hop on the firstLSP, generating forwarding data of each hop on the first LSP, and thensending the forwarding data of each hop on the first LSP to a nodedevice corresponding to each hop on the first LSP to completeestablishment of the first LSP; and

allocating, by the first service controller from first label spaceinformation of each hop on the second LSP, a label to each hop on thesecond LSP, determining incoming and outgoing interface information ofeach hop on the second LSP according to topology information of each hopon the second LSP, generating forwarding data of each hop on the secondLSP, and then sending the forwarding data of each hop on the second LSPto a node device corresponding to each hop on the second LSP to completeestablishment of the second LSP.

In an optional implementation manner of the foregoing method, before thedetermining, by a first service controller, each hop on an LSP from apreset ingress to a preset egress, the method includes: receiving, bythe first service controller, registration information sent by eachforwarding device in a network to which the first service controllerbelongs, where the registration information includes topologyinformation of the forwarding device and first label space informationof the forwarding device.

In an optional implementation manner of the foregoing method, the methodfurther includes: sending, by the first service controller, identifierinformation of each hop on the first LSP to the second servicecontroller for backup.

In an optional implementation manner of the foregoing method, the firstLSP and the second LSP are both bidirectional LSPs; or the first LSP andthe second LSP are both unidirectional LSPs.

In an optional implementation manner of the foregoing method, the firstLSP and the second LSP are both point-to-point P2P LSPs; or the firstLSP and the second LSP are both point-to-multipoint P2MP LSPs.

According to one aspect, this application further provides a servicecontroller, including:

a determining module, configured to determine each hop on an LSP from apreset ingress to a preset egress;

a first generating module, configured to allocate, from first labelspace information of each hop, a label to each hop, determine incomingand outgoing information of each hop according to topology informationof each hop, and generate forwarding data of each hop; and

a first sending module, configured to send the forwarding data of eachhop to a node device corresponding to each hop to complete establishmentof the LSP.

In an optional implementation manner of the foregoing servicecontroller, the determining module is specifically configured todetermine each hop on a first LSP and a second LSP that have aprimary/standby protection relationship from the preset ingress to thepreset egress.

In an optional implementation manner of the foregoing servicecontroller, the first generating module is specifically configured toallocate, from first label space information of each hop on the firstLSP, a label to each hop on the first LSP, determine incoming andoutgoing interface information of each hop on the first LSP according totopology information of each hop on the first LSP, and generateforwarding data of each hop on the first LSP; and

the first sending module is specifically configured to send theforwarding data of each hop on the first LSP to a node devicecorresponding to each hop on the first LSP to complete establishment ofthe first LSP.

In an optional implementation manner of the foregoing servicecontroller, the service controller further includes: a second sendingmodule, configured to send identifier information of each hop on thesecond LSP to a second service controller, so that the second servicecontroller allocates, from second label space information of each hop onthe second LSP, a label to each hop on the second LSP, determinesincoming and outgoing interface information of each hop on the secondLSP according to topology information of each hop on the second LSP,generates forwarding data of each hop on the second LSP, and then sendsthe forwarding data of each hop on the second LSP to a node devicecorresponding to each hop on the second LSP to complete establishment ofthe second LSP.

In an optional implementation manner of the foregoing servicecontroller, the service controller and the second service controller areconnected through another network except a first network to which theservice controller and the second service controller belong;

the determining module is more specifically configured to determine eachhop that is located in the first network on the first LSP from thepreset ingress to the preset egress, where the first LSP passes throughthe other network; and

the first generating module is more specifically configured to: triggerestablishment of a third LSP, allocate, from first label spaceinformation of each hop that is located in the first network on thefirst LSP, a label to each hop that is located in the first network onthe first LSP, determine incoming and outgoing interface information ofeach hop that is located in the first network on the first LSP accordingto topology information of each hop that is located in the first networkon the first LSP, stitch the first LSP and the third LSP, and generateforwarding data of each hop that is located in the first network andeach hop that is located in the other network on the first LSP, wherethe third LSP is an LSP that uses the service controller as an ingress,uses the second service controller as an egress, and passes through theother network.

In an optional implementation manner of the foregoing servicecontroller, the first generating module is more specifically configuredto allocate an incoming label to the service controller on the thirdLSP, where the incoming label is an outgoing label of a previous hop ofthe service controller on the first LSP; and allocate an outgoing labelto the second service controller on the third LSP, where the outgoinglabel is an incoming label of a next hop of the second servicecontroller on the first LSP, where each hop on the third LSP except theservice controller and the second service controller constitutes eachhop that is located in the other network on the first LSP.

In an optional implementation manner of the foregoing servicecontroller, the service controller and the second service controller areconnected through another network except a first network to which theservice controller and the second service controller belong;

the determining module is more specifically configured to determine eachhop that is located in the first network on the second LSP from thepreset ingress to the preset egress, where the second LSP passes throughthe other network; and

the second sending module is specifically configured to triggerestablishment of a fourth LSP, and send a stitching and bindingrelationship between the second LSP and the fourth LSP, identifierinformation of each hop that is located in the first network on thesecond LSP, and identifier information of an ingress of the fourth LSPto the second service controller, where the fourth LSP is an LSP thatuses the service controller as the ingress, uses the second servicecontroller as an egress, and passes through the other network.

In an optional implementation manner of the foregoing servicecontroller, the first generating module is specifically configured toallocate, from first label space information of each hop on the firstLSP, a label to each hop on the first LSP, determine incoming andoutgoing interface information of each hop on the first LSP according totopology information of each hop on the first LSP, and generateforwarding data of each hop on the first LSP; and allocate, from firstlabel space information of each hop on the second LSP, a label to eachhop on the second LSP, determine incoming and outgoing interfaceinformation of each hop on the second LSP according to topologyinformation of each hop on the second LSP, and generate forwarding dataof each hop on the second LSP; and

the first sending module is specifically configured to send theforwarding data of each hop on the first LSP to a node devicecorresponding to each hop on the first LSP to complete establishment ofthe first LSP, and send the forwarding data of each hop on the secondLSP to a node device corresponding to each hop on the second LSP tocomplete establishment of the second LSP.

In an optional implementation manner of the foregoing servicecontroller, the service controller further includes: a first receivingmodule, configured to receive registration information sent by eachforwarding device in a network to which the service controller belongs,where the registration information includes topology information of theforwarding device and first label space information of the forwardingdevice.

In an optional implementation manner of the foregoing servicecontroller, the service controller further includes: a third sendingmodule, configured to send identifier information of each hop on thefirst LSP to the second service controller for backup.

According to one aspect, this application further provides a servicecontroller, including:

a processor, configured to determine each hop on an LSP from a presetingress to a preset egress, allocate, from first label space informationof each hop, a label to each hop, determine incoming and outgoinginterface information of each hop according to topology information ofeach hop, and generate forwarding data of each hop; and

a sender, configured to send the forwarding data of each hop, which isgenerated by the processor, to a node device corresponding to each hopto complete establishment of the LSP.

According to another aspect, this application provides a label switchingpath establishment method, including:

receiving, by a second service controller, identifier information, whichis sent by a first service controller, of each hop on a second LSP,where the second LSP is an LSP, which is determined by the first servicecontroller, from a preset ingress to a preset egress;

allocating, by the second service controller from second label spaceinformation of each hop on the second LSP, a label to each hop on thesecond LSP, determining incoming and outgoing interface information ofeach hop on the second LSP according to topology information of each hopon the second LSP, and generating forwarding data of each hop on thesecond LSP; and

sending, by the second service controller, the forwarding data of eachhop on the second LSP to a node device corresponding to each hop on thesecond LSP to complete establishment of the second LSP.

In an optional implementation manner of the foregoing method, the firstservice controller and the second service controller are connectedthrough another network except a first network to which the firstservice controller and the second service controller belong;

the receiving, by a second service controller, identifier information,which is sent by a first service controller, of each hop on a second LSPincludes: receiving, by the second service controller from the firstservice controller, a stitching and binding relationship between thesecond LSP and a fourth LSP, identifier information of each hop that islocated in the first network on the second LSP, and identifierinformation of an ingress of the fourth LSP, where the fourth LSP is anLSP that is established upon triggering by the first service controller,uses the first service controller as the ingress, uses the secondservice controller as an egress, and passes through the other network.

In an optional implementation manner of the foregoing method, theallocating, by the second service controller from second label spaceinformation of each hop on the second LSP, a label to each hop on thesecond LSP, determining incoming and outgoing interface information ofeach hop on the second LSP according to topology information of each hopon the second LSP, and generating forwarding data of each hop on thesecond LSP includes:

allocating, by the second service controller from second label spaceinformation of each hop that is located in the first network on thesecond LSP, a label to each hop that is located in the first network onthe second LSP, determining incoming and outgoing interface informationof each hop that is located in the first network on the second LSPaccording to topology information of each hop that is located in thefirst network on the second LSP, stitching the second LSP and the fourthLSP, and generating forwarding data of each hop that is located in thefirst network and each hop that is located in the other network on thesecond LSP.

In an optional implementation manner of the foregoing method, thestitching, by the second service controller, the second LSP and thefourth LSP includes:

allocating, by the second service controller, an incoming label to thefirst service controller on the fourth LSP, where the incoming label isan outgoing label of a previous hop of the first service controller onthe second LSP; and

allocating, by the second service controller, an outgoing label to thesecond service controller on the fourth LSP, where the outgoing label isan incoming label of a next hop of the second service controller on thesecond LSP, where

each hop on the fourth LSP except the first service controller and thesecond service controller constitutes each hop that is located in theother network on the second LSP.

In an optional implementation manner of the foregoing method, before thereceiving, by a second service controller, identifier information, whichis sent by a first service controller, of each hop on a second LSP, themethod includes:

receiving, by the second service controller, registration informationsent by each forwarding device in a network to which the second servicecontroller belongs, where the registration information includes topologyinformation of the forwarding device and second label space informationof the forwarding device.

In an optional implementation manner of the foregoing method, the methodfurther includes: receiving, by the second service controller,identifier information, which is sent by the first service controller,of each hop on a first LSP, where the first LSP is another LSP, which isdetermined by the first service controller, from the preset ingress tothe preset egress, and the first LSP and the second LSP have aprimary/standby protection relationship.

According to another aspect, this application further provides a servicecontroller, including:

a second receiving module, configured to receive identifier information,which is sent by a first service controller, of each hop on a secondLSP, where the second LSP is an LSP, which is determined by the firstservice controller, from a preset ingress to a preset egress;

a second generating module, configured to allocate, from second labelspace information of each hop on the second LSP, a label to each hop onthe second LSP, determine incoming and outgoing interface information ofeach hop on the second LSP according to topology information of each hopon the second LSP, and generate forwarding data of each hop on thesecond LSP; and

a fourth sending module, configured to send the forwarding data of eachhop on the second LSP to a node device corresponding to each hop on thesecond LSP to complete establishment of the second LSP.

In an optional implementation manner of the foregoing servicecontroller, the first service controller and the service controller areconnected through another network except a first network to which thefirst service controller and the service controller belong; and

the second receiving module is specifically configured to receive, fromthe first service controller, a stitching and binding relationshipbetween the second LSP and a fourth LSP, identifier information of eachhop that is located in the first network on the second LSP, andidentifier information of an ingress of the fourth LSP, where the fourthLSP is an LSP that is established upon triggering by the first servicecontroller, uses the first service controller as the ingress, uses theservice controller as an egress, and passes through the other network.

In an optional implementation manner of the foregoing servicecontroller, the second generating module is specifically configured to:allocate, from second label space information of each hop that islocated in the first network on the second LSP, a label to each hop thatis located in the first network on the second LSP, determine incomingand outgoing interface information of each hop that is located in thefirst network on the second LSP according to topology information ofeach hop that is located in the first network on the second LSP, stitchthe second LSP and the fourth LSP, and generate forwarding data of eachhop that is located in the first network and each hop that is located inthe other network on the second LSP.

In an optional implementation manner of the foregoing servicecontroller, the second generating module is more specifically configuredto allocate an incoming label to the first service controller on thefourth LSP, where the incoming label is an outgoing label of a previoushop of the first service controller on the second LSP, and allocate anoutgoing label to the service controller on the fourth LSP, where theoutgoing label is an incoming label of a next hop of the servicecontroller on the second LSP, where each hop on the fourth LSP exceptthe first service controller and the service controller constitutes eachhop that is located in the other network on the second LSP.

In an optional implementation manner of the foregoing servicecontroller, the service controller further includes: a third receivingmodule, configured to receive registration information sent by eachforwarding device in a network to which the service controller belongs,where the registration information includes topology information of theforwarding device and second label space information of the forwardingdevice.

In an optional implementation manner of the foregoing servicecontroller, the service controller further includes: a fourth receivingmodule, configured to receive identifier information, which is sent bythe first service controller, of each hop on a first LSP, where thefirst LSP is another LSP, which is determined by the first servicecontroller, from the preset ingress to the preset egress, and the firstLSP and the second LSP have a primary/standby protection relationship.

According to another aspect, this application further provides a servicecontroller, including:

a receiver, configured to receive identifier information, which is sentby a first service controller, of each hop on a second LSP, where thesecond LSP is an LSP, which is determined by the first servicecontroller, from a preset ingress to a preset egress;

a processor, configured to allocate, from second label space informationof each hop on the second LSP, a label to each hop on the second LSP,determine incoming and outgoing interface information of each hop on thesecond LSP according to topology information of each hop on the secondLSP, and generate forwarding data of each hop on the second LSP; and

a sender, configured to send the forwarding data of each hop on thesecond LSP to a node device corresponding to each hop on the second LSPto complete establishment of the second LSP.

According to still another aspect, this application provides a dataforwarding method, including:

receiving, by a forwarding device, forwarding data, which is sent by aservice controller, of the forwarding device on a label switching path(LSP) from a preset ingress to a preset egress, where the forwardingdata of the forwarding device includes a label that the servicecontroller allocates to the forwarding device from label spaceinformation of the forwarding device, and incoming and outgoinginterface information that the service controller determines for theforwarding device according to topology information of the forwardingdevice; and

forwarding, by the forwarding device, data according to the forwardingdata of the forwarding device.

In an optional implementation manner of the foregoing method, theservice controller includes a first service controller and/or a secondservice controller; the LSP includes a first LSP and/or a second LSP oftwo LSPs that have a primary/standby protection relationship, where eachhop on the first LSP is determined by the first service controller andeach hop on the second LSP is determined by the first service controllerand provided for the second service controller; and the label spaceinformation of the forwarding device includes first label spaceinformation and/or a second label space; and

the receiving, by a forwarding device, forwarding data, which is sent bya service controller, of the forwarding device on an LSP from a presetingress to a preset egress includes:

receiving, by the forwarding device, forwarding data, which is sent bythe first service controller, of the forwarding device on the first LSPfrom the preset ingress to the preset egress; and/or

receiving, by the forwarding device, forwarding data, which is sent bythe second service controller, of the forwarding device on the secondLSP from the preset ingress to the preset egress.

In an optional implementation method of the foregoing method, before thereceiving, by a forwarding device, forwarding data, which is sent by aservice controller, of the forwarding device on a label switching path(LSP) from a preset ingress to a preset egress, the method includes:

sending, by the forwarding device, first registration information to thefirst service controller, where the first registration informationincludes the topology information of the forwarding device and the firstlabel space information of the forwarding device; and

sending, by the forwarding device, second registration information tothe second service controller, where the second registration informationincludes the topology information about the forwarding device and thesecond label space information of the forwarding device.

In an optional implementation manner of the foregoing method, theforwarding device is the preset ingress; and

the forwarding, by the forwarding device, data according to theforwarding data of the forwarding device includes: forwarding, by theforwarding device, the data according to the forwarding data of theforwarding device on the first LSP and the forwarding data of theforwarding device on the second LSP.

In an optional implementation manner of the foregoing method, theforwarding, by the forwarding device, the data according to theforwarding data of the forwarding device on the first LSP and theforwarding data of the forwarding device on the second LSP includes:

forwarding, by the forwarding device, the data according to theforwarding data of the forwarding device on the first LSP if theforwarding device discovers that the first service controller is normal;and

forwarding, by the forwarding device, the data according to theforwarding data of the forwarding device on the second LSP if theforwarding device discovers that the first service controller is faulty.

According to still another aspect, this application further provides aforwarding device, including:

a fifth receiving module, configured to receive forwarding data, whichis sent by a service controller, of the forwarding device on a labelswitching path (LSP) from a preset ingress to a preset egress, where theforwarding data of the forwarding device includes a label that theservice controller allocates to the forwarding device from label spaceinformation of the forwarding device, and incoming and outgoinginterface information that the service controller determines for theforwarding device, according to topology information of the forwardingdevice; and

a fifth sending module, configured to forward data according to theforwarding data of the forwarding device.

In an optional implementation manner of the foregoing forwarding device,the service controller includes a first service controller and/or asecond service controller; the LSP includes a first LSP and/or a secondLSP of two LSPs that have a primary/standby protection relationship,where each hop on the first LSP is determined by the first servicecontroller and each hop on the second LSP is determined by the firstservice controller and provided for the second service controller; andthe label space information of the forwarding device includes firstlabel space information and/or a second label space; and

the fifth receiving module is specifically configured to receiveforwarding data, which is sent by the first service controller, of theforwarding device on the first LSP from the preset ingress to the presetegress; and/or is specifically configured to receive forwarding data,which is sent by the second service controller, of the forwarding deviceon the second LSP from the preset ingress to the preset egress.

In an optional implementation manner of the foregoing forwarding device,the forwarding device further includes: a sixth sending module,configured to send first registration information to the first servicecontroller and send second registration information to the secondservice controller, where the first registration information includesthe topology information of the forwarding device and the first labelspace information of the forwarding device, and the second registrationinformation includes the topology information of the forwarding deviceand the second label space information of the forwarding device.

In an optional implementation manner of the foregoing forwarding device,the forwarding device is the preset ingress; and

the fifth sending module is specifically configured to forward the dataaccording to the forwarding data of the forwarding device on the firstLSP and the forwarding data of the forwarding device on the second LSP.

In an optional implementation manner of the foregoing forwarding device,the fifth sending module is more specifically configured to forward thedata according to the forwarding data of the forwarding device on thefirst LSP if it is discovered that the first service controller isnormal, and forward the data according to the forwarding data of theforwarding device on the second LSP if it is discovered that the firstservice controller is faulty.

According to still another aspect, this application further provides aforwarding device, including:

a receiver, configured to receive forwarding data, which is sent by aservice controller, of the forwarding device on a label switching path(LSP) from a preset ingress to a preset egress, where the forwardingdata of the forwarding device includes a label that the servicecontroller allocates to the forwarding device from label spaceinformation of the forwarding device, and incoming and outgoinginterface information that the service controller determines for theforwarding device according to topology information of the forwardingdevice; and

a sender, configured to forward data according to the forwarding data ofthe forwarding device, which is received by the receiver.

According to the label switching path establishment method and theservice controller provided by this application in one aspect, theservice controller determines each hop on an LSP from a preset ingressto a preset egress, allocates a label to each hop, determines incomingand outgoing interface information of each hop, generates forwardingdata of each hop, and then sends the forwarding data of each hop to anode device corresponding to each hop, so that each node device on theLSP can forward data according to the forwarding data sent by theservice controller and there is no need to periodically send soft statepackets, such as Hello, Path, and Resv, between node devices on the LSP,which alleviates load of the node devices and helps increase the numberof RSVP-TE LSPs that each node device is capable of supporting.

According to the label switching path establishment method and theservice controller provided by this application in another aspect, whenthere are two service controllers that work in hot backup mode, theother service controller determines each hop on an LSP from a presetingress to a preset egress, while the service controller provided bythis embodiment receives identifier information, provided by the otherservice controller, of each hop on the LSP, allocates a label to eachhop, determines incoming and outgoing interface information of each hop,generates forwarding data of each hop, and then sends the forwardingdata of each hop to a node device corresponding to each hop, so thateach node device on the LSP can forward data according to the forwardingdata sent by the service controller provided by this embodiment andthere is no need to periodically send soft state packets, such as Hello,Path, and Resv, between node devices on the LSP, which alleviates loadof the node devices and helps increase the number of RSVP-TE LSPs thateach node device is capable of supporting.

According to the data forwarding method and the forwarding deviceprovided by this application in still another aspect, the forwardingdevice, as a hop on an LSP from a preset ingress to a preset egress,receives forwarding data, which is sent by a service controller, of theforwarding device on the LSP from the preset ingress to the presetegress, generates a forwarding entry according the forwarding data, andforwards data according to the forwarding entry, so that there is noneed to periodically send soft state packets, such as Hello, Path, andResv, between the forwarding device and nodes on the LSP, whichalleviates load of the forwarding device and helps increase the numberof RSVP-TE LSPs that the forwarding device is capable of supporting.

BRIEF DESCRIPTION OF THE DRAWINGS

To describe the technical solutions in the embodiments of the presentinvention more clearly, the following briefly introduces theaccompanying drawings required for describing the embodiments.Apparently, the accompanying drawings in the following description showsome embodiments of the present invention, and persons of ordinary skillin the art may still derive other drawings from these accompanyingdrawings without creative efforts.

FIG. 1 is a flowchart of an LSP establishment method according to anembodiment of the present invention;

FIG. 2 is a flowchart of an LSP establishment method according toanother embodiment of the present invention;

FIG. 3 is a flowchart of a data forwarding method according to anembodiment of the present invention;

FIG. 4A to FIG. 4D are schematic diagrams of an LSP establishment methodaccording to an embodiment of the present invention;

FIG. 5A to FIG. 5F are schematic diagrams of an LSP establishment methodaccording to another embodiment of the present invention;

FIG. 6 is a schematic structural diagram of a service controlleraccording to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of a service controlleraccording to another embodiment of the present invention;

FIG. 8 is a schematic structural diagram of a service controlleraccording to still another embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a service controlleraccording to still another embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a service controlleraccording to still another embodiment of the present invention;

FIG. 11 is a schematic structural diagram of a service controlleraccording to still another embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a forwarding deviceaccording to an embodiment of the present invention; and

FIG. 13 is a schematic structural diagram of a forwarding deviceaccording to another embodiment of the present invention.

DETAILED DESCRIPTION

To make the objectives, technical solutions, and advantages of theembodiments of the present invention clearer, the following clearlydescribes the technical solutions in the embodiments of the presentinvention with reference to the accompanying drawings in the embodimentsof the present invention. Apparently, the described embodiments are apart rather than all of the embodiments of the present invention. Allother embodiments obtained by persons of ordinary skill in the art basedon the embodiments of the present invention without creative effortsshall fall within the protection scope of the present invention.

Conventionally, in order to establish an LSP, forwarding devices in anetwork need to run a dynamic signaling protocol, for example, RSVP-TE,and soft state packets such as Hello, Path, and Resv need to beperiodically sent between node devices to maintain status information ofa link and an LSP between nodes, which causes heavy load to the nodedevices and affects the number of RSVP-TE LSPs that can be supported.With respect to this problem, the following embodiments of the presentinvention provide a solution. A main idea of the following embodimentsis as follows: A service controller is separately set in a network. Theservice controller is a node device in the network and other nodedevices except the service controller in the network are used asforwarding devices (Forwarder). The service controller determines path(Hop) information of each LSP (that is, determines each hop on the LSP),allocates a label to each hop on the LSP, determines incoming andoutgoing interface information and the like for each hop on the LSP,generates forwarding data of each hop, and then sends the forwardingdata of each hop to a node device corresponding to each hop. In thisway, unlike the conventional solution in which a dynamic signalingprotocol needs to be run and soft state packets such as Hello, Path, andResv need to be periodically sent to maintain status information of alink and an LSP between node devices, each node device on the LSP candirectly forward data according to the forwarding data sent by theservice controller and only needs to receive the forwarding data sent bythe service controller, which alleviates burden of the node devices andhelps increase the number of RSVP-TE LSPs that a node device is capableof supporting. Further, because the service controller determines eachhop on an LSP and calculates forwarding data of each hop in acentralized manner, a user does not need to configure RSVP-TEconfigurations explicitly on each node device, which simplifiescomplexity of user configuration and maintainability and alleviates theuser's configuration burden.

The foregoing network and a network involved in the followingembodiments of the present invention may be a virtual cluster system,but no limitation is posed thereon.

FIG. 1 is a flowchart of an LSP establishment method provided by anembodiment of the present invention. As shown in FIG. 1, the methodprovided by this embodiment includes:

Step 101: A first service controller determines each hop on an LSP froma preset ingress to a preset egress.

An ingress and an egress of each LSP may be preset by a user or anadministrator. Optionally, the ingress or the egress may be a forwardingdevice or may be the first service controller.

A process for the first service controller to determine each hop on theLSP from the preset ingress to the preset egress is actually a processfor the first service controller to calculate path information for theLSP from the preset ingress to the preset egress. For example, it isassumed that the ingress and the egress are a forwarding device A and aforwarding device D respectively. Hops that the first service controllerdetermines for the LSP from the forwarding device A to the forwardingdevice D are the forwarding device A, a forwarding device B, aforwarding device C, and the forwarding device D, which is equivalent tothat path information that the first service controller calculates forthe LSP from the forwarding device A to the forwarding device B is: theforwarding device A→the forwarding device B→the forwarding device C→theforwarding device D.

Optionally, the first service controller may use an algorithm similar toa Path Computation Element (PCE) algorithm, a Constraint Shortest PathFirst (CSPF) algorithm, or the like to determine each hop on the LSP. Itis noted herein that an existing PCE is a method of offline pathcalculation and does not include operations of allocating a label andgenerating forwarding data after each hop on an LSP is determined.However, although the first service controller provided by thisembodiment uses the algorithm similar to the PCE to determine each hopon an LSP, a focus lies in a process of allocating a label andgenerating forwarding data after each hop on the LSP is determined,which is different from the existing PCE.

Step 102: The first service controller allocates, from first label spaceinformation of each hop, a label to each hop, determines incoming andoutgoing interface information of each hop according to topologyinformation of each hop, generates forwarding data of each hop, andsends the forwarding data of each hop to a node device corresponding toeach hop to complete establishment of the LSP.

It is noted herein that the node device corresponding to each hop oneach LSP in the embodiments of the present invention may be a forwardingdevice, and may also be the first service controller or a second servicecontroller.

In this embodiment, before step 101, the method includes: receiving, bythe first service controller, registration information sent byforwarding devices in a network to which the first service controllerbelongs, where the registration information includes topology (topo)information of the forwarding devices and first label space informationof the forwarding devices. In other words, after the forwarding devicesin the network to which the first service controller belongs join thenetwork, the forwarding devices register their own topology informationand first label space information with the first service controller inadvance. The topology information includes but is not limited tointerface information of the forwarding devices, such as an interfaceindex and a media access control (MAC) address. Here, the first labelspace information of each forwarding device refers to label spaceinformation that each forwarding device registers with the first servicecontroller. Each forwarding device may further include other label spaceinformation besides the first label space information.

That is, the first service controller stores the topology informationand the first label space information of each forwarding device in thenetwork. In addition, the first service controller also stores its owntopology information and label space information. Therefore, the firstservice controller stores the topology information and the first labelspace information of each hop on the LSP from the preset ingress to thepreset egress.

In this way, after determining each hop on the LSP from the presetingress to the preset egress, the first service controller can acquirethe first label space information of each hop and the topologyinformation of each hop according to identifier information of each hop,allocate, from the first label space information of each hop, the labelto each hop, and determines the incoming and outgoing interfaceinformation of each hop according to the topology information of eachhop, so that the forwarding data of each hop is generated. That thefirst service controller allocates, from first label space informationof each hop, a label to each hop includes: allocating an incoming labeland/or an outgoing label to each hop. Specifically, if this hop is theingress, the first service controller allocates, from first label spaceinformation of this hop, only an outgoing label to this hop; if this hopis the egress, the first service controller allocates, from first labelspace information of this hop, only an incoming label to this hop; ifthis hop is a forwarding device except the ingress and the egress, thefirst service controller allocates, from first label space informationof this hop, an incoming label and an outgoing label to this hop at thesame time. That the first service controller determines incoming andoutgoing interface information of each hop according to topologyinformation of each hop mainly includes: determining, by the firstservice controller according to the topology information of each hop, anindex of an incoming interface, a media access control (MAC) address ofthe incoming interface, an index of an outgoing interface, a MAC addressof the outgoing interface, and like information of each hop.

It can be seen from the foregoing description that the forwarding dataof each hop includes label information of each hop and the incoming andoutgoing interface information of each hop. The forwarding data of everyhop on the LSP from the preset ingress to the preset egress constitutesentire forwarding data of the LSP.

Then the first service controller sends the forwarding data of each hopto the node device corresponding to each hop, so that each node deviceon the LSP from the preset ingress to the preset egress receives its ownforwarding data (generally, the forwarding data is also referred to as aforwarding entry) and then forwards data according to the forwardingdata. For example, information in a next hop label forwarding entry(NHLFE) is from the forwarding data sent by the first servicecontroller, mainly including information about an outgoing label and anoutgoing interface. For another example, information in an incominglabel map (ILM) table is from the forwarding data sent by the firstservice controller, mainly including information about an incoming labeland an incoming interface.

Conventionally, generating forwarding data (mainly referring to labelinformation of each hop) of an LSP is mainly allocating the forwardingdata locally by each forwarding device by running a dynamic signalingprotocol such as LDP/RSVP-TE, and the forwarding data is sent to anupstream forwarding device of the forwarding device. In this manner ofautomatic calculation and allocation by using a dynamic protocol, softstate packets such as Hello, Path, and Resv need to be periodically sentbetween forwarding devices to maintain link status information and LSPstatus information, which causes heavy burden to the forwarding devicesand affects the number of RSVP-TE LSPs that each forwarding device iscapable of supporting. A process of creating the forwarding data of theLSP by using the dynamic signaling protocol such as LDP/RSVP-TE ismarked as a control plane of the dynamic signaling protocol such asLDP/RSVP-TE, while a process of forwarding data according to theforwarding data is marked as a data plane of the dynamic signalingprotocol such as LDP/RSVP-TE. Therefore, in this embodiment, the firstservice controller creates the forwarding data of the LSP in acentralized manner and sends the forwarding data of each hop on the LSPto each hop on the LSP. Each hop on the LSP may not run the controlplane of the dynamic signaling protocol such as LDP/RSVP-TE and onlyneeds to forward the data according to the forwarding data sent by thefirst service controller, so that the soft state packets such as Hello,Path, and Resv do not need to be periodically sent between the hops onthe LSP, which alleviates load of the node devices and helps increasethe number of RSVP-TE LSPs that each node device is capable ofsupporting.

Further, because the forwarding data of the LSP is created by the firstservice controller in a centralized manner in this embodiment, the firstservice controller can determine whether to create a unidirectional LSPor a bidirectional LSP in the network as required. For example, aftereach hop on an LSP is determined (that is, path information iscalculated) by using the PCE/CSPF, a unidirectional LSP can be acquiredby allocating a label to an incoming interface of each forwardingdevice. Optionally, on this basis, path information in the otherdirection may be acquired by reversing the calculated path informationand an incoming label is applied for each forwarding device based on thereversed path information to acquire a reverse LSP. For example, it isassumed that an LSP is: a forwarding device A→a forwarding device B→aforwarding device C→a forwarding device D. A reverse LSP acquired is:the forwarding device D→the forwarding device C→the forwarding deviceB→the forwarding device A.

Optionally, because the forwarding data of the LSP is created by thefirst service controller in a centralized manner in this embodiment,whether to create a point-to-point (P2P) LSP or a point-to-multipoint(P2MP) LSP in the network may be determined as required. For example, ifthe PCE/CSPF is used to calculate P2MP path information, in the P2MPpath information, one incoming interface may correspond to multipleoutgoing interfaces, that is, multiple next hops. Therefore, labelsallocated to the multiple next hops correspond to one incoming interfaceof the node, that is, one ILM corresponds to multiple NHLFEs. Then aP2MP LSP can be acquired.

Optionally, because the forwarding data of the LSP is created by thefirst service controller in a centralized manner in this embodiment,whether to create a single LSP or two LSPs that have a primary/standbyprotection relationship may be determined as required, which is moreflexible.

In an optional implementation manner of this embodiment, the firstservice controller determines each hop on a first LSP and a second LSPthat have a primary/standby protection relationship from the presetingress to the preset egress. That is, the first service controllerdetermines to create two LSPs that have a primary/standby protectionrelationship and determines each hop on each LSP (that is, determinespath information of each LSP). Either LSP of the first LSP and thesecond LSP can be used as a primary LSP and the other as a standby LSP.

In an optional implementation manner of this embodiment, only oneservice controller, that is, the first service controller, exists in theentire network. Based on the foregoing technical solution of creatingtwo LSPs from the preset ingress to the preset egress, an optionalimplementation manner of step 102 includes: The first service controllerallocates, from first label space information of each hop on the firstLSP, a label to each hop on the first LSP, determines incoming andoutgoing interface information of each hop on the first LSP according totopology information of each hop on the first LSP, generates forwardingdata of each hop on the first LSP, and then sends the forwarding data ofeach hop on the first LSP to a node device corresponding to each hop onthe first LSP to complete establishment of the first LSP; the firstservice controller allocates, from first label space information of eachhop on the second LSP, a label to each hop on the second LSP, determinesincoming and outgoing interface information of each hop on the secondLSP according to topology information of each hop on the second LSP,generates forwarding data of each hop on the second LSP, and then sendsthe forwarding data of each hop on the second LSP to a node devicecorresponding to each hop on the second LSP to complete establishment ofthe second LSP. It is noted herein that, in this implementation manner,a process in which the first service controller completes establishmentof the first LSP and a process in which the first service controllercompletes establishment of the second LSP may be concurrently executed,which helps improve LSP establishment efficiency.

In the foregoing implementation manner, only one service controller,that is, a first service controller, exists in the network. The firstservice controller calculates a first LSP and a second LSP from a presetingress to a preset egress, allocates a label to each hop on the firstLSP and the second LSP, determines incoming and outgoing interfaceinformation of each hop, generates forwarding data of each hop, and thensends the forwarding data of each hop on the first LSP and the secondLSP to a node device corresponding to each hop on the first LSP and thesecond LSP. In this way, on the one hand, each node device on each LSPcan forward data according to the forwarding data sent by the firstservice controller so that there is no need to periodically send softstate packets such as Hello, Path, and Resv between node devices of thehops on each LSP, which alleviates load of the node devices of the hopsand helps increase the number of RSVP-TE LSPs that each node device iscapable of supporting; on the other hand, based on the two LSPs thatwork in mutual backup mode, when one LSP is faulty, a switchover to theother LSP is implemented, which helps improve a success rate of dataforwarding. Further, because the first service controller determineseach hop on an LSP and calculates forwarding data of each hop in acentralized manner, a user does not need to configure RSVP-TEconfigurations explicitly on each node device, which simplifiescomplexity of user configuration and maintainability and alleviates theuser's configuration burden.

In an optional implementation manner of this embodiment, two servicecontrollers that have a primary/standby relationship, that is, the firstservice controller and the second service controller, may be configuredin the entire network. In the embodiments of the present invention, thefirst service controller is used as a primary service controller and thesecond service controller is used as a standby service controller, butno limitation is posed thereon. Based on the foregoing technicalsolution of creating two LSPs from the preset ingress to the presetegress, an optional implementation manner of step 102 includes: Thefirst service controller allocates, from first label space informationof each hop on the first LSP, a label to each hop on the first LSP,determines incoming and outgoing interface information of each hop onthe first LSP according to topology information of each hop on the firstLSP, generates forwarding data of each hop on the first LSP, and thensends the forwarding data of each hop on the first LSP to a node devicecorresponding to each hop on the first LSP to complete establishment ofthe first LSP. That is, when the first service controller calculates twoLSPs from the preset ingress to the preset egress, the first servicecontroller selects one LSP (the first LSP is used as an example in thisembodiment) from the two LSPs, allocates a label to each hop on theselected LSP, determines incoming and outgoing interface information ofeach hop on the selected LSP, forms forwarding data of each hop on theselected LSP, and sends the forwarding data to each hop to completeestablishment of the selected LSP. That is, the first service controlleris responsible for completing establishment of one LSP.

Based on the foregoing description, the method provided by thisembodiment further includes: The first service controller sendsidentifier information of each hop on the second LSP to the secondservice controller, so that the second service controller allocates,from second label space information of each hop on the second LSP, alabel to each hop on the second LSP, determines incoming and outgoinginterface information of each hop on the second LSP according totopology information of each hop on the second LSP, generates forwardingdata of each hop on the second LSP, and then sends the forwarding dataof each hop on the second LSP to a node device corresponding to each hopon the second LSP to complete establishment of the second LSP. That is,when the first service controller calculates two LSPs from the presetingress to the preset egress, the first service controller providesidentifier information of each hop on the other LSP (that is, pathinformation of the other LSP) for the second service controller. Thesecond service controller is responsible for completing establishment ofthe other LSP. A process in which the second service controllercompletes establishment of the other LSP is similar to a process inwhich the first service controller completes establishment of one LSP ofthe two LSPs, and details are not described herein again. Here, secondlabel space information of each forwarding device refers to label spaceinformation that each forwarding device registers with the secondservice controller.

It is noted herein that the first label space information and the secondlabel space information of each forwarding device are not overlapped.That is, in a case in which two service controllers exist, the labelspace information that each forwarding device registers with the firstservice controller is not intersected with the label space informationthat each forwarding device registers with the second servicecontroller, which can ensure that labels allocated by the two servicecontrollers to each hop on each LSP do not conflict. However, topologyinformation that each forwarding device registers with the first servicecontroller is the same as topology information that each forwardingdevice registers with the second service controller.

In the foregoing implementation manner, the first service controller andthe second service controller may be connected directly or may beconnected indirectly. Further, the first service controller and thesecond service controller may be indirectly connected through aforwarding device in a network to which the first service controller andthe second service controller belong; or the first service controllerand the second service controller may also be indirectly connectedthrough another network except the network to which the first servicecontroller and the second service controller belong, that is, the firstservice controller and the second service controller may traverseanother network. For ease of description, in the embodiments of thepresent invention, the network to which the first service controller andthe second service controller belong is called a first network.

In an optional implementation manner of this embodiment, the firstservice controller and the second service controller may be indirectlyconnected through the forwarding device in the first network to whichthe first service controller and the second service controller belong.In this case, each hop on the first LSP and each hop on the second LSPare both node devices in the first network to which the first servicecontroller and the second service controller belong.

In an optional implementation manner of this embodiment, the firstservice controller and the second service controller may also beindirectly connected through the other network except the first networkto which the first service controller and the second service controllerbelong. In this case, one of the first LSP and the second LSP that aredetermined by the first service controller from the preset ingress tothe preset egress needs to traverse the other network.

If the first LSP is the LSP traversing the other network, animplementation manner of that the first service controller determineseach hop on the first LSP from the preset ingress to the preset egressincludes: The first service controller determines each hop that islocated in the first network on the first LSP from the preset ingress tothe preset egress, where the first LSP passes through the other network,that is, a part of node devices on the first LSP are located in theother network. Optionally, the first service controller may further usean algorithm similar to the PCE or CSPF to determine each hop that islocated in the first network on the first LSP that passes through theother network. If the first LSP passes through the other network, anexemplary implementation manner is that the first LSP passes through thefirst service controller and the second service controller, and thefirst service controller and the second service controller are connectedby traversing the other network. Accordingly, an implementation mannerof that the first service controller allocates, from first label spaceinformation of each hop on the first LSP, a label to each hop on thefirst LSP, determines incoming and outgoing interface information ofeach hop on the first LSP according to topology information of each hopon the first LSP, and generates forwarding data of each hop on the firstLSP includes: The first service controller triggers establishment of athird LSP, where the third LSP is an LSP that uses the first servicecontroller as an ingress, uses the second service controller as anegress, and passes through the other network, where each hop on thethird LSP except the ingress and the egress constitutes each hop that islocated in the other network on the first LSP; and then the firstservice controller allocates, from first label space information of eachhop that is located in the first network on the first LSP, a label toeach hop that is located in the first network on the first LSP,determines incoming and outgoing interface information of each hop thatis located in the first network on the first LSP according to topologyinformation of each hop that is located in the first network on thefirst LSP, stitches the first LSP and the third LSP, and generatesforwarding data of each hop that is located in the first network andeach hop that is located in the other network on the first LSP.

A process in which the first service controller triggers establishmentof the third LSP may be as follows: All node devices in the othernetwork run a dynamic signaling protocol, for example, RSVP-TE. In thiscase, the first service controller may complete, by means of using anexisting technology, establishment of the third LSP with the secondservice controller through the node devices in the other network, wherea status of the third LSP may be maintained by using the soft statepackets such as Hello, Path, and Resv, and the label, incoming andoutgoing interface information, and like information of each hop on thethird LSP may be locally allocated and sent to a previous hop by eachhop by using a Resv packet. A process in which the first servicecontroller establishes the third LSP may further be as follows: The nodedevices in the other network register their own topology information andfirst label space information with the first service controller and thenthe first service controller performs centralized control to completeestablishment of the third LSP. A process in which the first servicecontroller controls establishment of the third LSP is the same as aprocess in which the first service controller controls establishment ofthe first LSP. Specifically, the first service controller determineseach hop on the third LSP, allocates, from first label space informationof each hop on the third LSP, a label to each hop on the third LSP, anddetermines incoming and outgoing interface information of each hop onthe third LSP according to topology information of each hop on the thirdLSP to complete establishment of the third LSP. It is noted herein thatthe first LSP does not need to concern about other node devices on thethird LSP except the first service controller and the second servicecontroller, labels and incoming and outgoing interface information thatare allocated to these node devices, or the like, that is, the first LSPdoes not need to know this information.

The foregoing process in which the first service controller stitches thefirst LSP and the third LSP includes: The first service controllerallocates an incoming label to the ingress (that is, the first servicecontroller) on the third LSP, where the incoming label is an outgoinglabel of a previous hop of the first service controller on the firstLSP, and allocates an outgoing label to the egress (that is, the secondservice controller) on the third LSP, where the outgoing label is anincoming label of a next hop of the second service controller on thefirst LSP, and each hop on the third LSP except the first servicecontroller and the second service controller constitutes each hop thatis located in the other network on the first LSP.

If the second LSP is the LSP traversing the other network, animplementation manner of that the first service controller determineseach hop on the second LSP from the preset ingress to the preset egressincludes: The first service controller determines each hop that islocated in the first network on the second LSP from the preset ingressto the preset egress, where the second LSP passes through the othernetwork, that is, a part of node devices on the second LSP are locatedin the other network. Optionally, the first service controller mayfurther use an algorithm similar to the PCE or CSPF to determine eachhop that is located in the first network on the second LSP that passesthrough the other network. If the second LSP passes through the othernetwork, an exemplary implementation manner is that the second LSPpasses through the first service controller and the second servicecontroller, and the first service controller and the second servicecontroller are connected by traversing the other network. Accordingly,an implementation manner of that the first service controller sendsidentifier information of each hop on the second LSP to the secondservice controller includes: The first service controller triggersestablishment of a fourth LSP, where the fourth LSP is an LSP that usesthe first service controller as an ingress, uses the second servicecontroller as an egress, and passes through the other network, and eachhop on the fourth LSP except the ingress and the egress constitutes eachhop that is located in the other network on the second LSP; and then thefirst service controller sends a stitching and binding relationshipbetween the second LSP and the fourth LSP, identifier information ofeach hop that is located in the first network on the second LSP, andidentifier information of the ingress of the fourth LSP (that is,identifier information of the first service controller) to the secondservice controller. The stitching and binding relationship between thesecond LSP and the fourth LSP is indication information used to instructthe second service controller to stitch the second LSP and the fourthLSP. The second service controller may obtain each hop that is locatedin the first network on the second LSP, according to the identifierinformation, which is sent by the first service controller, of each hopthat is located in the first network on the second LSP, so as toallocate a label to each hop that is located in the first network on thesecond LSP and determine incoming and outgoing interface information.For the second service controller, it may locally acquire identifierinformation of the egress of the fourth LSP. Therefore, after receivingthe identifier information, which is sent by the first servicecontroller, of the ingress of the fourth LSP, the second servicecontroller can obtain each hop on the fourth LSP (that is, obtain pathinformation of the fourth LSP), so as to acquire the label and incomingand outgoing interface information of each hop on the fourth LSP. Thesecond service controller may stitch, according to the stitching andbinding relationship between the second LSP and the fourth LSP, which issent by the first service controller, the second LSP and the fourth LSPafter the label of each hop on the second LSP and the fourth LSP isdetermined, and generate forwarding data of each hop that is located inthe first network and each hop that is located in the any other networkon the second LSP. A process in which the first service controllerestablishes the fourth LSP is similar to a process in which the firstservice controller establishes the third LSP, and details are notdescribed herein again.

The foregoing process in which the second service controller stitchesthe second LSP and the fourth LSP includes: The second servicecontroller allocates an incoming label to the ingress (that is, thefirst service controller) on the fourth LSP, where the incoming label isan outgoing label of a previous hop of the first service controller onthe second LSP, and allocates an outgoing label to the egress (that is,the second service controller) on the fourth LSP, where the outgoinglabel is an incoming label of a next hop of the second servicecontroller on the second LSP, and each hop on the fourth LSP except thefirst service controller and the second service controller constituteseach hop that is located in the other network on the second LSP.

In an optional implementation manner of this embodiment, the firstservice controller may further send identifier information of each hopon the first LSP to the second service controller for backup. In thisway, when the first service controller or the first LSP is faulty, thesecond service controller can perform rerouting according to the storedidentifier information of each hop on the first LSP, to prevent a newLSP from being the same as the first LSP, so as to maximally increase anLSP convergence speed.

It is noted herein that the foregoing identifier information of each hopmay be an IP address of each hop and like information, which mayuniquely identify an incoming interface and an outgoing interface of aforwarding device corresponding to each hop. In the foregoingimplementation manner, a first service controller calculates each hop ona first LSP and a second LSP from a preset ingress to a preset egress.Then the first service controller and a second service controllerrespectively allocate a label to each hop on the first LSP and thesecond LSP, determine incoming and outgoing interface information ofeach hop, generate forwarding data of each hop, and then send theforwarding data of each hop on the first LSP and the second LSP to anode device corresponding to each hop on the first LSP and the secondLSP. In this way, on the one hand, each node device on each LSP canforward data according to the received forwarding data so that there isno need to periodically send soft state packets such as Hello, Path, andResv between node devices of the hops on each LSP, which alleviates loadof the node devices of the hops and helps increase the number of RSVP-TELSPs that each node device is capable of supporting; on the other hand,based on the two LSPs that work in mutual backup mode, when one LSP isfaulty, a switchover to the other LSP is implemented, which helpsimprove a success rate of data forwarding. Further, because the firstservice controller or the second service controller determines each hopon an LSP and calculates forwarding data of each hop in a centralizedmanner, a user does not need to configure RSVP-TE configurationsexplicitly on each node device, which simplifies complexity of userconfiguration and maintainability and alleviates the user'sconfiguration burden.

FIG. 2 is a flowchart of an LSP establishment method provided by anotherembodiment of the present invention. In this embodiment, a first servicecontroller and a second service controller exist in a network at thesame time, and the first service controller and the second servicecontroller work in hot backup mode. As shown in FIG. 2, the methodprovided by this embodiment includes:

Step 201: The second service controller receives identifier information,which is sent by the first service controller, of each hop on a secondLSP, where the second LSP is an LSP, which is determined by the firstservice controller, from a preset ingress to a preset egress.

Specifically, the first service controller determines each hop on twoLSPs from the preset ingress to the preset egress, that is, each hop ona first LSP and the second LSP. Optionally, the first service controllermay use an algorithm similar to a PCE algorithm, a CSFP algorithm, orthe like to separately determine each hop on the first LSP and thesecond LSP, where the first LSP and the second LSP have aprimary/standby relationship. Then the first service controller sendsthe identifier information of each hop on the second LSP to the secondservice controller, so that the second service controller is responsiblefor completing establishment of the second LSP. The first servicecontroller is responsible for completing establishment of the first LSP.

For a process in which the first service controller is responsible forcompleting establishment of the first LSP, reference may be made todescriptions in the foregoing embodiment.

Step 202: The second service controller allocates, from second labelspace information of each hop on the second LSP, a label to each hop onthe second LSP, determines incoming and outgoing interface informationof each hop on the second LSP according to topology information of eachhop on the second LSP, and generates forwarding data of each hop on thesecond LSP.

After receiving the identifier information of each hop on the secondLSP, the second service controller can determine each hop on the secondLSP (that is, determine path information of the second LSP). Then thesecond service controller allocates, from the second label spaceinformation of each hop on the second LSP, a label to each hop on thesecond LSP, determines the incoming and outgoing interface informationof each hop on the second LSP according to the topology information ofeach hop on the second LSP, and generates the forwarding data of eachhop on the second LSP. That the second service controller allocates,from the second label space information of each hop on the second LSP, alabel to each hop on the second LSP includes: allocating an incominglabel and/or an outgoing label to each hop. Specifically, if this hop isan ingress on the second LSP, the second service controller allocates,from second label space information of this hop, an outgoing label tothis hop; if this hop is an egress on the second LSP, the second servicecontroller allocates, from second label space information of this hop,an incoming label to this hop; if this hop is another forwarding deviceon the second LSP except the ingress and the egress, the second servicecontroller allocates, from second label space information of this hop,an incoming label and an outgoing label to this hop at the same time.That the second service controller determines incoming and outgoinginterface information of each hop on the second LSP according totopology information of each hop on the second LSP mainly includes:determining, by the second service controller according to the topologyinformation of each hop on the second LSP, an index of an incominginterface, a MAC address of the incoming interface, an index of anoutgoing interface, a MAC address of the outgoing interface, and likeinformation of each hop on the second LSP.

It can be seen from the foregoing description that the forwarding dataof each hop on the second LSP includes label information and theincoming and outgoing interface information of each hop. The forwardingdata of each hop on the second LSP constitutes complete forwarding dataof the second LSP.

In an optional implementation manner of this embodiment, before step201, the method includes: receiving, by the second service controller,registration information sent by each forwarding device in a network towhich the second service controller belongs, where the registrationinformation includes topology information of the forwarding device andsecond label space information of the forwarding device. The secondlabel space information of each forwarding device refers to label spaceinformation that each forwarding device registers with the secondservice controller. Each forwarding device may further include otherlabel space information, for example, first label space informationregistered with the first service controller. The first label spaceinformation and the second label space information of each forwardingdevice are not intersected or overlapped.

Step 203: The second service controller sends the forwarding data ofeach hop on the second LSP to a node device corresponding to each hop onthe second LSP to complete establishment of the second LSP.

The second service controller sends the forwarding data of each hop onthe second LSP to the node device corresponding to each hop on thesecond LSP, so that after receiving its own forwarding data, each nodedevice on the second LSP can forward data according to the receivedforwarding data. The forwarding data may include various types ofinformation in an NHLFE and/or an ILM.

It is noted herein that, when the first LSP and the second LSP exist inthe network at the same time, the first LSP is preferably used for dataforwarding, and data forwarding is switched to the second LSP when thefirst LSP is faulty, which does not affect a forwarding plane and canimprove a success rate of data forwarding. An ingress of the first LSP(that is, the ingress of the second LSP) detects a status of the firstservice controller. When it is discovered that the first servicecontroller is faulty, data forwarding is switched to the second LSP andthe second service controller is upgraded to a primary control server.Optionally, after a fault of the first service controller is rectified,the ingress on the first LSP can perform control again to upgrade thefirst service controller to the primary control server. When the faultof the first service controller cannot be rectified or is still notrectified after a preset time, each hop on the first LSP can delete,according to aging time, forwarding data corresponding to the first LSP.

It can be seen from the foregoing description that, in a case in whichtwo service controllers having a primary/standby relationship, that is,a first service controller and a second service controller, areconfigured in a network, after the first service controller determineseach hop on two LSPs having a primary/standby relationship, that is, afirst LSP and a second LSP, the first service controller and the secondservice controller are respectively responsible for determiningforwarding data of each hop on the first LSP and the second LSP andsending the forwarding data of each hop to a node device correspondingto each hop to complete establishment of the first LSP and the secondLSP. In this way, on the one hand, each node device on each LSP canforward data according to the received forwarding data so that there isno need to periodically send soft state packets such as Hello, Path, andResv between node devices of the hops on each LSP, which alleviates loadof the node devices of the hops and helps increase the number of RSVP-TELSPs that each node device is capable of supporting; on the other hand,based on the two LSPs that work in mutual backup mode, when one LSP isfaulty, a switchover to the other LSP is implemented, which helpsimprove a success rate of data forwarding. Further, because the firstservice controller or the second service controller determines each hopon an LSP and calculates forwarding data of each hop in a centralizedmanner, a user does not need to configure RSVP-TE configurationsexplicitly on each node device, which simplifies complexity of userconfiguration and maintainability and alleviates the user'sconfiguration burden.

The first service controller and the second service controller may beconnected directly or may be connected indirectly. Further, the firstservice controller and the second service controller may be indirectlyconnected through another forwarding device in a first network to whichthe first service controller and the second service controller belong,or may be indirectly connected through another network except the firstnetwork to which the first service controller and the second servicecontroller belong.

In an optional implementation manner of this embodiment, the firstservice controller and the second service controller are connectedthrough the other network except the first network to which the firstservice controller and the second service controller belong. In thiscase, an optional implementation manner of step 201 includes: The secondservice controller receives, from the first service controller, astitching and binding relationship between the second LSP and a fourthLSP, identifier information of each hop that is located in the firstnetwork on the second LSP, and identifier information of an ingress(that is, the first service controller) of the fourth LSP. The stitchingand binding relationship between the second LSP and the fourth LSP isindication information used to instruct the second service controller tostitch the second LSP and the fourth LSP. The fourth LSP is an LSP thatis established by the first service controller, uses the first servicecontroller as the ingress, uses the second service controller as anegress, and passes through the other network, where each hop on thefourth LSP constitutes each hop that is located in the other network onthe second LSP. For a process in which the first service controllerestablishes the fourth LSP, reference may be made to descriptions of aprocess in which the first service controller establishes the third LSPin the foregoing embodiment.

Based on the foregoing description, an optional implementation manner ofstep 202 includes: The second service controller allocates, from secondlabel space information of each hop that is located in the first networkon the second LSP, a label to each hop that is located in the firstnetwork on the second LSP, determines incoming and outgoing interfaceinformation of each hop that is located in the first network on thesecond LSP according to topology information of each hop that is locatedin the first network on the second LSP, stitches the second LSP and thefourth LSP, and generates forwarding data of each hop that is located inthe first network and each hop that is located in the other network onthe second LSP. Specifically, the second service controller may obtain,according to the identifier information, which is sent by the firstservice controller, of each hop that is located in the first network onthe second LSP, each hop that is located in the first network on thesecond LSP, so as to allocate the label to each hop that is located inthe first network on the second LSP and determine the incoming andoutgoing interface information. For the second service controller, itmay locally acquire identifier information of the egress of the fourthLSP. Therefore, after receiving the identifier information, which issent by the first service controller, of the ingress of the fourth LSP,the second service controller can obtain each hop on the fourth LSP(that is, obtain path information of the fourth LSP), so as to acquirethe label and incoming and outgoing interface information of each hop onthe fourth LSP. The second service controller may stitch, according tothe stitching and binding relationship between the second LSP and thefourth LSP, which is sent by the first service controller, the secondLSP and the fourth LSP after the label of each hop on the second LSP andthe fourth LSP is determined, and generate the forwarding data of thesecond LSP.

The foregoing process in which the second service controller stitchesthe second LSP and the fourth LSP includes: The second servicecontroller allocates an incoming label to the ingress (that is, thefirst service controller) on the fourth LSP, where the incoming label isan outgoing label of a previous hop of the first service controller onthe second LSP, and allocates an outgoing label to the egress (that is,the second service controller) on the fourth LSP, where the outgoinglabel is an incoming label of a next hop of the second servicecontroller on the second LSP, and each hop on the fourth LSP except thefirst service controller and the second service controller constituteseach hop that is located in the other network on the second LSP.

In an optional implementation manner of this embodiment, the secondservice controller may further receive identifier information, which issent by the first service controller, of each hop on the first LSP andstore the identifier information of each hop on the first LSP. The firstLSP is the other LSP determined by the first service controller from thepreset ingress to the preset egress, and the first LSP and the secondLSP have the primary/standby protection relationship. In this way, whenthe first service controller is faulty or the first LSP is faulty, thesecond service controller can perform rerouting according to the storedidentifier information of each hop on the first LSP, to prevent a newroute from being the same as the first LSP, so as to maximally increasean LSP convergence speed.

In the foregoing implementation manner, a first service controllercalculates each hop on a first LSP and a second LSP from a presetingress to a preset egress. Then the first service controller and asecond service controller respectively allocate a label to each hop onthe first LSP and the second LSP, determine incoming and outgoinginterface information of each hop, generate forwarding data of each hop,and then send the forwarding data of each hop on the first LSP and thesecond LSP to a node device corresponding to each hop on the first LSPand the second LSP. In this way, on the one hand, the node device ofeach hop on each LSP can forward data according to the receivedforwarding data so that there is no need to periodically send soft statepackets such as Hello, Path, and Resv between node devices of the hopson each LSP, which alleviates load of the node devices of the hops andhelps increase the number of RSVP-TE LSPs that each node device iscapable of supporting; on the other hand, based on the two LSPs thatwork in mutual backup mode, when one LSP is faulty, a switchover to theother LSP is implemented, which helps improve a success rate of dataforwarding. Further, because the first service controller or the secondservice controller determines each hop on an LSP and calculatesforwarding data of each hop in a centralized manner, a user does notneed to configure RSVP-TE configurations explicitly on each node device,which simplifies complexity of user configuration and maintainabilityand alleviates the user's configuration burden.

FIG. 3 is a flowchart of a data forwarding method provided by anembodiment of the present invention. As shown in FIG. 3, the methodprovided by this embodiment includes:

Step 301: A forwarding device receives forwarding data, which is sent bya service controller, of the forwarding device on an LSP from a presetingress to a preset egress.

The forwarding data of the forwarding device includes a label that theservice controller allocates to the forwarding device from label spaceinformation of the forwarding device, and incoming and outgoinginformation that the service controller determines for the forwardingdevice according to topology information of the forwarding device.

Step 302: The forwarding device forwards data according to the foregoingforwarding data of the forwarding device.

In an optional implementation manner of this embodiment, the servicecontroller includes a first service controller and/or a second servicecontroller; the LSP includes a first LSP and/or a second LSP of two LSPsthat have a primary/standby protection relationship, where each hop onthe first LSP is determined by the first service controller and each hopon the second LSP is determined by the first service controller andprovided for the second service controller; and accordingly, the labelspace information of the forwarding device includes first label spaceinformation and/or second label space information.

Specifically, if the service controller is the first service controller,the LSP refers to the first LSP and the label space information of theforwarding device is the first label space information. In this case,step 301 is specifically as follows: The forwarding device receivesforwarding data, which is sent by the first service controller, of theforwarding device on the first LSP from the preset ingress to the presetegress. The forwarding device is a hop on the first LSP, and theforwarding data of the forwarding device includes a label that the firstservice controller allocates to the forwarding device from the firstlabel space information of the forwarding device, and incoming andoutgoing interface information that the first service controllerdetermines for the forwarding device according to the topologyinformation of the forwarding device.

If the service controller is the second service controller, the LSP isthe second LSP and the label space information of the forwarding deviceis the second label space information. In this case, step 301 isspecifically as follows: The forwarding device receives forwarding data,which is sent by the second service controller, of the forwarding deviceon the second LSP from the preset ingress to the preset egress. Theforwarding device is a hop on the second LSP, and the forwarding data ofthe forwarding device includes a label that the second servicecontroller allocates to the forwarding device from the second labelspace information of the forwarding device, and incoming and outgoinginterface information that the second service controller determines forthe forwarding device according to the topology information of theforwarding device.

In addition, if the forwarding device is the preset ingress or thepreset egress and two service controllers having a primary/standbyrelationship, that is, the first service controller and the secondservice controller, are configured in a network at the same time, theforwarding device receives forwarding data of the forwarding device,which is sent by the first service controller and the second servicecontroller at the same time. Specifically, the forwarding devicereceives forwarding data, which is sent by the first service controller,of the forwarding device on the first LSP and also receives forwardingdata, which is sent by the second service controller, of the forwardingdevice on the second LSP. The forwarding data, which is sent by thefirst service controller, of the forwarding device includes: a labelthat the first service controller allocates to the forwarding devicefrom the first label space information of the forwarding device, andincoming and outgoing interface information that the first servicecontroller determines for the forwarding device according to thetopology information of the forwarding device. The forwarding data,which is sent by the second service controller, of the forwarding deviceincludes: a label that the second service controller allocates to theforwarding device from the second label space information of theforwarding device, and incoming and outgoing interface information thatthe second service controller determines for the forwarding deviceaccording to the topology information of the forwarding device.

It can be seen from the foregoing description that, if the forwardingdevice provided by this embodiment is located on the first LSP, dataforwarding can be performed according to the forwarding data, which issent by the first service controller, of the forwarding device on thefirst LSP; if the forwarding device provided by this embodiment islocated on the second LSP, data forwarding can be performed according tothe forwarding data, which is sent by the second service controller, ofthe forwarding device on the second LSP.

In an optional implementation manner of this embodiment, before step301, the method includes: the forwarding device sends first registrationinformation to the first service controller, where the firstregistration information includes the topology information of theforwarding device and the first label space information of theforwarding device; and the forwarding device sends second registrationinformation to the second service controller, where the secondregistration information includes the topology information of theforwarding device and the second label space information of theforwarding device.

In an optional implementation manner of this embodiment, if theforwarding device is the preset ingress, an optional implementationmanner of step 302 includes: The forwarding device separately forwardsthe data according to the forwarding data of the forwarding device onthe first LSP and the forwarding data of the forwarding device on thesecond LSP. In a case in which the first service controller is notfaulty, the forwarding device preferably chooses to forward the dataaccording to the forwarding data of the forwarding device on the firstLSP. When it is monitored that the first service controller is faulty,the forwarding device forwards the data according to the forwarding dataof the forwarding device on the second LSP, that is, data forwarding isswitched from the first LSP to the second LSP, which improves a successrate of data forwarding.

It can be seen from the foregoing description that, in the dataforwarding method provided by this embodiment, a forwarding device andanother forwarding device do not need to send soft state packets such asHello, Path, and Resv to each other, and data can be forwarded accordingto received forwarding data, which ensures light load of the forwardingdevice and increases the number of RSVP-TE LSPs that the forwardingdevice is capable of supporting. In addition, because a servicecontroller determines each hop on an LSP and calculates forwarding dataof each hop in a centralized manner, a user does not need to configureRSVP-TE configurations explicitly on a forwarding device, whichsimplifies complexity of user configuration and maintainability andalleviates the user's configuration burden.

The following uses a virtual cluster system shown in FIG. 4A as anexample to describe a process of an LSP establishment method provided bythe present invention. As shown in FIG. 4A, the virtual cluster systemincludes: a node 41, a node 42, a forwarding device 43, a forwardingdevice 44, a forwarding device 45, a forwarding device 46, a firstservice controller 47, and a second service controller 48. The node 41is connected to the forwarding device 43; the forwarding device 43 isfurther connected to the forwarding device 44 and the first servicecontroller 47; the forwarding device 44 is further connected to theforwarding device 45; the forwarding device 45 is further connected tothe forwarding device 46; the forwarding device 46 is further connectedto the node 42 and the second service controller 48; and the firstservice controller 47 is connected to the second service controller 48.As shown in FIG. 4A, the first service controller 47 is connected to thesecond service controller 48 by using a dashed line, which indicatesthat the first service controller 47 and the second service controller48 may be connected directly or may be connected indirectly. In thisembodiment, it is assumed that the first service controller 47 and thesecond service controller 48 are connected directly. It is assumed thata preset ingress is the forwarding device 43 and a preset egress is theforwarding device 46.

Step 1: Each forwarding device registers with the service controllers.As shown in FIG. 4A, each of the forwarding devices 43 to 46 sends firstregistration information (represented by a solid line with an arrow inFIG. 4A) to the first service controller 47, and each of the forwardingdevices 43 to 46 sends second registration information (represented by adash-dotted line with an arrow in FIG. 4A) to the second servicecontroller 48. The first registration information sent by the forwardingdevices 43 to 46 includes their own first label space information andtopology information. The second registration information sent by theforwarding devices 43 to 46 includes their own second label spaceinformation and topology information. The first label space informationis not intersected with the second label space information.

It is noted herein that, if there is only one service controller in thevirtual cluster system, the forwarding devices need to register onlywith the service controller.

Step 2: The service controllers calculate path information of an LSP,that is, determine each hop on the LSP. As shown in FIG. 4B, the firstservice controller 47 uses an algorithm mechanism similar to a PCEalgorithm, a CSPF algorithm, or the like to calculate two LSPs having aprimary/standby protection relationship, that is, a first LSP and asecond LSP, for the virtual cluster system. As shown in FIG. 4B, pathinformation of the first LSP includes: the forwarding device 43→theforwarding device 44→the forwarding device 45→the forwarding device 46,and path information of the second LSP includes: the forwarding device43→the first service controller 47→the second service controller 48→theforwarding device 46.

It is noted herein that the first service controller 47 may alsocalculate an LSP from the forwarding device 43 to the forwarding device46 for the virtual cluster system.

As shown in FIG. 4B, the first service controller 47 synchronizes thepath information of the first LSP and the path information of the secondLSP to the second service controller 48.

Step 3: The service controllers allocate a label to each Hop (that is,each hop) and generate complete forwarding data of the LSPs. The firstservice controller 47 allocates a label to each Hop on the first LSP,determines incoming and outgoing interface information of each Hop,generates forwarding data of each Hop, and constitutes completeforwarding data of the first LSP by using the forwarding data of allHops. In this embodiment, only the label of each Hop is shown. In thiscase, the complete forwarding data of the first LSP is shown in FIG. 4C.In the same way, the second service controller 48 allocates a label toeach Hop on the second LSP, determines incoming and outgoing interfaceinformation of each Hop, generates forwarding data of each Hop, andconstitutes complete forwarding data of the second LSP by using theforwarding data of all Hops. In this embodiment, only the label of eachHop is shown. In this case, the complete forwarding data of the secondLSP is shown in FIG. 4C.

Step 4: The service controllers send the forwarding data, which iscorresponding to each Hop, in the complete forwarding data of the LSPsto a forwarding device corresponding to this Hop. The first servicecontroller 47 splits the complete forwarding data of the first LSP,which is calculated in step 3, according to the forwarding devices andsends forwarding data that belongs to each forwarding device to thecorresponding forwarding device. A final delivery result is shown inFIG. 4D, that is, the first service controller 47 sends “--/100” to theforwarding device 43, sends “100/200” to the forwarding device 44, sends“200/3” to the forwarding device 45, and sends “3/--” to the forwardingdevice 46. In the same way, the second service controller 48 splits thecomplete forwarding data of the second LSP, which is calculated in step3, according to the forwarding devices and sends forwarding data thatbelongs to each forwarding device to the corresponding forwardingdevice. A final delivery result is shown in FIG. 4D, that is, the secondservice controller 48 sends “--/1000” to the forwarding device 43, sends“1000/2000” to the first service controller 47, sends “2000/3” to thesecond service controller 48, and sends “3/--” to the forwarding device46.

For the forwarding devices, they only need to directly forward, afterreceiving the forwarding data sent by the service controllers, data on aforwarding plane according to the forwarding data. It can be seen thatthe forwarding devices do not need to run a control plane any longer andonly need to run the forwarding plane, and unlike the conventionalsolution, there is no need to send soft state packets such as Hello,Path, and Resv, thereby alleviating burden and supporting more RSVP-TELSPs.

Optionally, as a primary service controller (Primary Controller), thefirst service controller 47 controls establishment of the first LSP andthe second LSP in the virtual cluster system. After the first servicecontroller 47 is faulty, the forwarding plane is not affected andtraffic is switched to the second LSP. If a fault of the first servicecontroller 47 cannot be rectified, the forwarding devices 43 to 46 canage and delete, on their own, forwarding data that belongs to the firstservice controller 47 on the first LSP. In addition, after the firstservice controller 47 is faulty, the forwarding device 43 can performcontrol to upgrade the second service controller 48 that is used as astandby service controller (Standby Controller) to a new primary servicecontroller.

In this embodiment, on a basis that a control plane is separated from aforwarding plane, a service controller is used to generate forwardingdata in a centralized manner and a forwarding device does not need torun the control plane so that the forwarding device is freed anddedicated to data forwarding. The following beneficial effects areachieved compared with the conventional solution: 1. The servicecontroller calculates complete forwarding data of an LSP in acentralized manner, and only corresponding forwarding data and someother necessary link information are transmitted between the servicecontroller and the forwarding device, which saves system resourcesoccupied by running a dynamic signaling protocol. The saved resourcesmay be used to support more LSP forwarding, thereby improving an MPLSforwarding capability that the forwarding device is capable ofsupporting and increasing the number of MPLS LSPs that the forwardingdevice is capable of supporting. 2. The service controller performscentralized control to generate the complete forwarding data of the LSP,which further improves manageability of a user for the MPLS LSPs, canbetter make a policy with respect to LSPs, and further decreases networkoperation and maintenance costs.

The following uses a network composed of a virtual cluster system shownin FIG. 5A as an example to describe a process of an LSP establishmentmethod provided by the present invention. As shown in FIG. 5A, thenetwork includes: a node 51, a node 52, a forwarding device 53, aforwarding device 54, a forwarding device 55, a forwarding device 56, afirst service controller 57, a second service controller 58, a node 59,a node 60, and a node 61, where the node 51, the node 52, the forwardingdevice 53, the forwarding device 54, the forwarding device 55, theforwarding device 56, the first service controller 57, and the secondservice controller 58 belong to the same virtual cluster system, whilethe node 59, the node 60, and the node 61 belong to a node outside thevirtual cluster system. As shown in FIG. 5A, the node 51 is connected tothe forwarding device 53; the forwarding device 53 is further connectedto the forwarding device 54 and the first service controller 57; theforwarding device 54 is further connected to the forwarding device 55;the forwarding device 55 is further connected to the forwarding device56; the forwarding device 56 is further connected to the node 52 and thesecond service controller 58; the first service controller 57 is furtherconnected to the node 59; the node 59 is further connected to node 60;the node 60 is further connected to node 61; and the node 61 is furtherconnected to the second service controller 58. In this embodiment, thefirst service controller 57 and the second service controller 58 areconnected through the node 59, the node 60, and the node 61. The node59, the node 60, and the node 61 do not belong to the virtual clustersystem to which the first service controller 57 and the second servicecontroller 58 belong, that is, the first service controller 57 and thesecond service controller 58 are connected by traversing anothernetwork. It is assumed that a preset ingress is the forwarding device 53and a preset egress is the forwarding device 56.

Step 1: Each of the forwarding devices registers with the servicecontrollers. As shown in FIG. 5A, the forwarding devices 53 to 56 sendfirst registration information (represented by a solid line with anarrow in FIG. 5A) to the first service controller 57, and the forwardingdevices 53 to 56 send second registration information (represented by adashed line with an arrow in FIG. 5A) to the second service controller58. The first registration information sent by the forwarding devices 53to 56 includes their own first label space information and topologyinformation. The second registration information sent by the forwardingdevices 53 to 56 includes their own second label space information andtopology information. The first label space information is notintersected with the second label space information.

It is noted herein that, if there is only one service controller in thevirtual cluster system, the forwarding devices need to register onlywith the service controller.

Step 2: The service controllers calculate path information of an LSP,that is, determine each hop on the LSP. As shown in FIG. 5B, the firstservice controller 57 uses an algorithm mechanism similar to a PCEalgorithm, a CSPF algorithm, or the like to calculate two LSPs having aprimary/standby protection relationship, that is, a first LSP and asecond LSP, for the virtual cluster system. As shown in FIG. 5B, pathinformation of the first LSP includes: the forwarding device 53→thefirst service controller 57→the node 59→the second service controller58→the forwarding device 56. In this case, the first service controller57 determines only nodes that are located in the virtual cluster systemon the first LSP and does not concern about nodes that traverse theother network. Path information of the second LSP includes: theforwarding device 53→the forwarding device 54→the forwarding device55→the forwarding device 56.

It is noted herein that the first service controller 47 may alsocalculate an LSP from the forwarding device 53 to the forwarding device56 for the virtual cluster system.

As shown in FIG. 5B, the first service controller 57 synchronizes thepath information of the first LSP and the path information of the secondLSP to the second service controller 58.

Step 3: The server controllers trigger establishment of an LSP outside adomain. As shown in FIG. 5C, the first service controller 57 does notallocate a label to each hop on the first LSP immediately but triggers adynamic signaling protocol to establish a third LSP that traverses anexternal network. The third LSP uses the first service controller 57 asan ingress, uses the second service controller 58 as an egress, andpasses through the node 59, the node 60, and the node 61, as shown in anarc with an arrow in FIG. 5C. Labels of the first service controller 57,the node 59, the node 60, the node 61, and the second service controller58 may be locally allocated on their own and sent to their previous hopsby using a Resv packet. Respective labels are shown in FIG. 5C.

Step 4: The service controllers allocate a label to each Hop andgenerate complete forwarding data of the LSPs. The first servicecontroller 57 allocates a label to each Hop that is located in thevirtual cluster system on the first LSP, determines incoming andoutgoing interface information of each Hop, stitches the first LSP andthe third LSP, generates forwarding data of each Hop that is located inthe virtual cluster system and each Hop that is located outside thevirtual cluster system on the first LSP, and constitutes completeforwarding data of the first LSP by using the forwarding data of allHops. In this embodiment, only the label of each Hop is shown. In thiscase, the complete forwarding data of the first LSP is shown in FIG. 5D.A result of stitching the first LSP and the third LSP is: The firstservice controller 57 is assigned an incoming label as the ingress ofthe third LSP, where the incoming label is an outgoing label 1025 of theforwarding device 53 and the forwarding device 53 on the first LSP is anupstream node of the first service controller 57; and the second servicecontroller is assigned an outgoing label as the egress of the third LSP,where the outgoing label is an incoming label 3 of the forwarding device56 and the forwarding device 56 on the first LSP is a downstream node ofthe second service controller 58. In the same way, the second servicecontroller 58 allocates a label to each Hop on the second LSP,determines incoming and outgoing interface information of each Hop,generates forwarding data of each Hop, and constitutes completeforwarding data of the second LSP by using the forwarding data of allHops. In this embodiment, only the label of each Hop is shown. In thiscase, the complete forwarding data of the second LSP is shown in FIG.5D.

Step 5: The service controllers send the forwarding data, which iscorresponding to each Hop, in the complete forwarding data of the LSPsto a forwarding device corresponding to this Hop. The first servicecontroller 57 splits the complete forwarding data of the first LSP,which is calculated in step 4, according to the forwarding devices andsends forwarding data that belongs to each forwarding device to thecorresponding forwarding device. A final delivery result is shown inFIG. 5E, that is, the first service controller 57 sends “--/100” to theforwarding device 53, sends “100/1025” to the first service controller57, sends “1025/1026” to the node 59, sends “1026/1027” to the node 60,sends “1027/1028” to the node 61, sends “1028/3” to the second servicecontroller 58, and sends “3/--” to the forwarding device 56. In the sameway, the second service controller 48 splits the complete forwardingdata of the second LSP, which is calculated in step 4, according to theforwarding devices and sends forwarding data that belongs to eachforwarding device to the corresponding forwarding device. A finaldelivery result is shown in FIG. 5E, that is, the second servicecontroller 58 sends “--/1000” to the forwarding device 53, sends“1000/2000” to the forwarding device 54, sends “2000/3” to theforwarding device 55, and sends “3/--” to the forwarding device 56.

For the forwarding devices, they only need to directly forward, afterreceiving the forwarding data sent by the service controllers, data on aforwarding plane according to the forwarding data. It can be seen thatthe forwarding devices do not need to run a control plane any longer andonly need to run the forwarding plane, and unlike the conventionalsolution, there is no need to send soft state packets such as Hello,Path, and Resv, thereby alleviating burden and supporting more RSVP-TELSPs.

Optionally, as a primary service controller (Primary Controller), thefirst service controller 57 controls establishment of the first LSP andthe second LSP in the virtual cluster system. After the first servicecontroller 57 is faulty, the forwarding plane is not affected andtraffic is switched to the second LSP. If a fault of the first servicecontroller 57 cannot be rectified, the forwarding devices 53 to 56 canage and delete, on their own, forwarding data that belongs to the firstservice controller 57 on the first LSP. In addition, after the firstservice controller 57 is faulty, the forwarding device 53 can performcontrol to upgrade the second service controller 58 that is used as astandby service controller (Standby Controller) to a new primary servicecontroller.

In this embodiment, on a basis that a control plane is separated from aforwarding plane, a service controller is used to generate forwardingdata in a centralized manner and a forwarding device does not need torun the control plane so that the forwarding device is freed anddedicated to data forwarding. The following beneficial effects areachieved compared with the conventional solution: 1. The servicecontroller calculates complete forwarding data of an LSP in acentralized manner, and only corresponding forwarding data and someother necessary link information are transmitted between the servicecontroller and the forwarding device, which saves system resourcesoccupied by running a dynamic signaling protocol. The saved resourcesmay be used to support more LSP forwarding, thereby improving an MPLSforwarding capability that the forwarding device is capable ofsupporting and increasing the number of MPLS LSPs that the forwardingdevice is capable of supporting. 2. The service controller performscentralized control to generate the complete forwarding data of the LSP,which further improves manageability of a user for the MPLS LSPs, canbetter make a policy with respect to LSPs, and further decreases networkoperation and maintenance costs.

FIG. 6 is a schematic structural diagram of a service controllerprovided by an embodiment of the present invention. The servicecontroller provided by this embodiment may be used as the first servicecontroller in the foregoing manner embodiments. As shown in FIG. 6, theservice controller provided by this embodiment includes: a determiningmodule 601, a first generating module 602, and a first sending module603.

The determining module 601 is configured to determine each hop on an LSPfrom a preset ingress to a preset egress. The first generating module602 is connected to the determining module 601 and configured to:allocate, from first label space information of each hop determined bythe determining module 601, a label to each hop, determine incoming andoutgoing information of each hop according to topology information ofeach hop, and generate forwarding data of each hop. The first sendingmodule 603 is connected to the first generating module 602 andconfigured to send the forwarding data of each hop, which is generatedby the first generating module 602, to a node device corresponding toeach hop to complete establishment of the LSP.

The foregoing functional modules may be configured to executecorresponding processes in the foregoing method embodiments. Specificworking principles of the functional modules are not described hereinagain and reference may be made to descriptions of the methodembodiments for details.

The service controller provided by this embodiment determines each hopon an LSP from a preset ingress to a preset egress, allocates a label toeach hop, determines incoming and outgoing interface information of eachhop, generates forwarding data of each hop, and then sends theforwarding data of each hop to a node device corresponding to each hop,so that a node device of each hop on the LSP can forward data accordingto the forwarding data sent by the service controller and there is noneed to periodically send soft state packets such as Hello, Path, andResv between node devices of the hops on the LSP, which alleviates loadof the node devices and helps increase the number of RSVP-TE LSPs thateach node device is capable of supporting. Further, because the servicecontroller provided by this embodiment determines each hop on an LSP andcalculates forwarding data of each hop in a centralized manner, a userdoes not need to configure RSVP-TE configurations explicitly on eachnode device, which simplifies complexity of user configuration andmaintainability and alleviates the user's configuration burden.

FIG. 7 is a schematic structural diagram of a service controllerprovided by another embodiment of the present invention. This embodimentis implemented based on the embodiment shown in FIG. 6. As shown in FIG.7, the service controller provided by this embodiment also includes: adetermining module 601, a first generating module 602, and a firstsending module 603.

In this embodiment, the determining module 601 can be specificallyconfigured to determine each hop on a first LSP and a second LSP thathave a primary/standby protection relationship and are from a presetingress to a preset egress.

In an optional implementation manner of this embodiment, the firstgenerating module 602 can be specifically configured to: allocate, fromfirst label space information of each hop that is determined by thedetermining module 601 on the first LSP, a label to each hop on thefirst LSP, determine incoming and outgoing interface information of eachhop on the first LSP according to topology information of each hop onthe first LSP, and generate forwarding data of each hop on the firstLSP. Accordingly, the first sending module 603 can be specificallyconfigured to send the forwarding data of each hop on the first LSP,which is generated by the first generating module 602, to a node devicecorresponding to each hop on the first LSP to complete establishment ofthe first LSP.

As shown in FIG. 7, the service controller provided by this embodimentfurther includes a second sending module 604. The second sending module604 is connected to the determining module 601 and configured to sendidentifier information of each hop that is determined by the determiningmodule 601 on the second LSP to a second service controller, so that thesecond service controller allocates, from second label space informationof each hop on the second LSP, a label to each hop on the second LSP,determines incoming and outgoing interface information of each hop onthe second LSP according to topology information of each hop on thesecond LSP, generates forwarding data of each hop on the second LSP, andthen sends the forwarding data of each hop on the second LSP to a nodedevice corresponding to each hop on the second LSP to completeestablishment of the second LSP.

In an optional implementation manner of this embodiment, the servicecontroller provided by this embodiment and the second service controllerare connected through another network except a first network to whichthe service controller provided by this embodiment and the secondservice controller belong. Based on this, a process in which thedetermining module 601 determines each hop on the first LSP isspecifically as follows: The determining module 601 is more specificallyconfigured to determine each hop that is located in the first network onthe first LSP from the preset ingress to the preset egress, where thefirst LSP passes through the other network. Accordingly, the firstgenerating module 602 is more specifically configured to triggerestablishment of a third LSP, allocates, from first label spaceinformation of each hop that is located in the first network on thefirst LSP, a label to each hop that is located in the first network onthe first LSP, determines, incoming and outgoing interface informationof each hop that is located in the first network on the first LSPaccording to topology information of each hop that is located in thefirst network on the first LSP, stitches the first LSP and the thirdLSP, and generates forwarding data of each hop that is located in thefirst network and each hop that is located in the other network on thefirst LSP. The third LSP is an LSP that uses the service controllerprovided by this embodiment as an ingress, uses the second servicecontroller as an egress, and passes through the other network, whereeach hop on the third LSP except the ingress and the egress constituteseach hop that is located in the other network on the first LSP.

The first generating module 602 is more specifically configured toallocate an incoming label to the service controller provided by thisembodiment on the third LSP, where the incoming label is an outgoinglabel of a previous hop of the service controller provided by thisembodiment on the first LSP, and allocate an outgoing label to thesecond service controller on the third LSP, where the outgoing label isan incoming label of a next hop of the second service controller on thefirst LSP. Each hop on the third LSP except the service controllerprovided by this embodiment and the second service controllerconstitutes each hop that is located in the other network on the firstLSP.

In an optional implementation manner of this embodiment, the servicecontroller provided by this embodiment and the second service controllerare connected through another network except a first network to whichthe service controller provided by this embodiment and the secondservice controller belong. Based on this, a process in which thedetermining module 601 determines each hop on the second LSP isspecifically as follows: The determining module 601 is more specificallyconfigured to determine each hop that is located in the first network onthe second LSP from the preset ingress to the preset egress, where thesecond LSP passes through the other network. Accordingly, the secondsending module 604 can be specifically configured to triggerestablishment of a fourth LSP and send a stitching and bindingrelationship between the second LSP and the fourth LSP, identifierinformation of each hop that is located in the first network on thesecond LSP, and identifier information of an ingress of the fourth LSPto the second service controller. The stitching and binding relationshipbetween the second LSP and the fourth LSP is indication information usedto instruct the second service controller to stitch the second LSP andthe fourth LSP. The fourth LSP is an LSP that uses the servicecontroller provided by this embodiment as the ingress, uses the secondservice controller as an egress, and passes through the other network,where each hop on the fourth LSP except the ingress and the egressconstitutes each hop that is located in the other network on the secondLSP.

In an optional implementation manner of this embodiment, the firstgenerating module 602 can be specifically configured to allocate, fromfirst label space information of each hop that is determined by thedetermining module 601 on the first LSP, a label to each hop on thefirst LSP, determine incoming and outgoing interface information of eachhop on the first LSP according to topology information of each hop onthe first LSP, and generate forwarding data of each hop on the firstLSP; and allocate, from first label space information of each hop thatis determined by the determining module 601 on the second LSP, a labelto each hop on the second LSP, determine incoming and outgoing interfaceinformation of each hop on the second LSP according to topologyinformation of each hop on the second LSP, and generate forwarding dataof each hop on the second LSP. Accordingly, the first sending module 603can be specifically configured to send the forwarding data of each hopon the first LSP, which is generated by the first generating module 602,to a node device corresponding to each hop on the first LSP to completeestablishment of the first LSP, and send the forwarding data of each hopon the second LSP, which is generated by the first generating module602, to a node device corresponding to each hop on the second LSP tocomplete establishment of the second LSP.

As shown in FIG. 7, the service controller provided by this embodimentfurther includes a first receiving module 605. The first receivingmodule 605 is configured to receive registration information sent byeach forwarding device in a network to which the service controllerprovided by this embodiment belongs, where the registration informationincludes topology information of the forwarding device and first labelspace information of the forwarding device. The first receiving module605 is connected to the first generating module 602 and configured toprovide the topology information of the forwarding device and the firstlabel space information of the forwarding device for the firstgenerating module 602.

As shown in FIG. 7, the service controller provided by this embodimentfurther includes a third sending module 606. The third sending module606 is connected to the determining module 601 and configured to sendidentifier information of each hop that is determined by the determiningmodule 601 on the first LSP to the second service controller for backup.

The foregoing functional modules may be configured to executecorresponding processes in the foregoing method embodiments. Specificworking principles of the functional modules are not described hereinagain and reference may be made to descriptions of the methodembodiments for details.

The service controller provided by this embodiment determines each hopon an LSP from a preset ingress to a preset egress, allocates a label toeach hop, determines incoming and outgoing interface information of eachhop, generates forwarding data of each hop, and then sends theforwarding data of each hop to a node device corresponding to each hop,so that a node device of each hop on the LSP can forward data accordingto the forwarding data sent by the service controller and there is noneed to periodically send soft state packets such as Hello, Path, andResv between node devices of the hops on the LSP, which alleviates loadof the node devices and helps increase the number of RSVP-TE LSPs thateach node device is capable of supporting. Further, because the servicecontroller provided by this embodiment determines each hop on an LSP andcalculates forwarding data of each hop in a centralized manner, a userdoes not need to configure RSVP-TE configurations explicitly on eachnode device, which simplifies complexity of user configuration andmaintainability and alleviates the user's configuration burden.

FIG. 8 is a schematic structural diagram of a service controllerprovided by still another embodiment of the present invention. As shownin FIG. 8, the service controller provided by this embodiment includes aprocessor 801 and a sender 802.

The processor 801 is configured to determine each hop on an LSP from apreset ingress to a preset egress, allocate, from first label spaceinformation of each hop, a label to each hop, determine incoming andoutgoing interface information of each hop according to topologyinformation of each hop, and generate forwarding data of each hop. Thesender 802 is connected to the processor 801 and configured to send theforwarding data of each hop, which is generated by the processor 801, toa node device corresponding to each hop to complete establishment of theLSP.

In an optional implementation manner of this embodiment, the processor801 is specifically configured to determine each hop on a first LSP anda second LSP that have a primary/standby protection relationship and arefrom the preset ingress to the preset egress.

In an optional implementation manner of this embodiment, the processor801 is specifically configured to allocate, from first label spaceinformation of each hop that is determined on the first LSP, a label toeach hop on the first LSP, determine incoming and outgoing interfaceinformation of each hop on the first LSP according to topologyinformation of each hop on the first LSP, and generate forwarding dataof each hop on the first LSP. Accordingly, the sender 802 can bespecifically configured to send the forwarding data of each hop on thefirst LSP to a node device corresponding to each hop on the first LSP tocomplete establishment of the first LSP.

In an optional implementation manner of this embodiment, the sender 802can be further configured to send identifier information of each hopthat is determined by the processor 801 on the second LSP to a secondservice controller, so that the second service controller allocates,from second label space information of each hop on the second LSP, alabel to each hop on the second LSP, determines incoming and outgoinginterface information of each hop on the second LSP according totopology information of each hop on the second LSP, generates forwardingdata of each hop on the second LSP, and then sends the forwarding dataof each hop on the second LSP to a node device corresponding to each hopon the second LSP to complete establishment of the second LSP.

In an optional implementation manner of this embodiment, the servicecontroller provided by this embodiment and the second service controllerare connected through another network except a first network to whichthe service controller provided by this embodiment and the secondservice controller belong. Based on this, the processor 801 isspecifically configured to determine each hop that is located in thefirst network on the first LSP from the preset ingress to the presetegress, where the first LSP passes through the other network. Theprocessor 801 is specifically configured to trigger establishment of athird LSP, allocate, from first label space information of each hop thatis located in the first network on the first LSP, a label to each hopthat is located in the first network on the first LSP, determineincoming and outgoing interface information of each hop that is locatedin the first network on the first LSP according to topology informationof each hop that is located in the first network on the first LSP,stitch the first LSP and the third LSP, and generate forwarding data ofeach hop that is located in the first network and each hop that islocated in the other network on the first LSP, where the third LSP is anLSP that uses the service controller provided by this embodiment as aningress, uses the second service controller as an egress, and passesthrough the other network. Each hop on the third LSP except the ingressand the egress constitutes each hop that is located in the other networkon the first LSP.

In an optional implementation manner of this embodiment, the servicecontroller provided by this embodiment and the second service controllerare connected through another network except a first network to whichthe service controller provided by this embodiment and the secondservice controller belong. Based on this, the processor 801 isspecifically configured to determine each hop that is located in thefirst network on the second LSP from the preset ingress to the presetegress, where the second LSP passes through the other network. Thesender 802 is specifically configured to trigger establishment of afourth LSP and send a stitching and binding relationship between thesecond LSP and the fourth LSP, identifier information of each hop thatis located in the first network on the second LSP, and identifierinformation of an ingress of the fourth LSP to the second servicecontroller, where the fourth LSP is an LSP that uses the servicecontroller provided by this embodiment as the ingress, the secondservice controller as an egress, and passes through the other network.Each hop on the fourth LSP except the ingress and the egress constituteseach hop that is located in the other network on the second LSP. Thestitching and binding relationship between the second LSP and the fourthLSP is indication information used to instruct the second servicecontroller to stitch the second LSP and the fourth LSP.

In an optional implementation manner of this embodiment, the processor801 can be specifically configured to allocate, from first label spaceinformation of each hop on the first LSP, a label to each hop on thefirst LSP, determine incoming and outgoing interface information of eachhop on the first LSP according to topology information of each hop onthe first LSP, and generate forwarding data of each hop on the firstLSP; and allocate, from first label space information of each hop on thesecond LSP, a label to each hop on the second LSP, determine incomingand outgoing interface information of each hop on the second LSPaccording to topology information of each hop on the second LSP, andgenerate forwarding data of each hop on the second LSP. Accordingly, thesender 802 can be specifically configured to send the forwarding data ofeach hop on the first LSP, which is generated by the processor 801, to anode device corresponding to each hop on the first LSP to completeestablishment of the first LSP, and send the forwarding data of each hopon the second LSP, which is generated by the processor 801, to a nodedevice corresponding to each hop on the second LSP to completeestablishment of the second LSP.

As shown in FIG. 8, the service controller provided by this embodimentfurther includes a receiver 803. The receiver 803 is configured toreceive registration information sent by each forwarding device in anetwork to which the service controller provided by this embodimentbelongs, where the registration information includes topologyinformation of the forwarding device and first label space informationof the forwarding device. Optionally, the receiver 803 is connected tothe processor 801 and configured to provide the topology information ofthe forwarding device and the first label space information of theforwarding device for the processor 801.

In an optional implementation manner of this embodiment, the sender 802is further configured to send identifier information of each hop that isdetermined by the processor 801 on the first LSP to the second servicecontroller for backup.

The service controller provided by this embodiment may be configured toexecute corresponding processes in the foregoing method embodiments.Specific working principles of the service controller are not describedherein again and reference may be made to descriptions of the methodembodiments for details.

The service controller provided by this embodiment determines each hopon an LSP from a preset ingress to a preset egress, allocates a label toeach hop, determines incoming and outgoing interface information of eachhop, generates forwarding data of each hop, and then sends theforwarding data of each hop to a node device corresponding to each hop,so that a node device of each hop on the LSP can forward data accordingto the forwarding data sent by the service controller and there is noneed to periodically send soft state packets such as Hello, Path, andResv between node devices of the hops on the LSP, which alleviates loadof the node devices and helps increase the number of RSVP-TE LSPs thateach node device is capable of supporting. Further, because the servicecontroller provided by this embodiment determines each hop on an LSP andcalculates forwarding data of each hop in a centralized manner, a userdoes not need to configure RSVP-TE configurations explicitly on eachnode device, which simplifies complexity of user configuration andmaintainability and alleviates the user's configuration burden.

FIG. 9 is a schematic structural diagram of a service controllerprovided by still another embodiment of the present invention. As shownin FIG. 9, the service controller provided by this embodiment includes:a second receiving module 901, a second generating module 902, and afourth sending module 903.

The second receiving module 901 is configured to receive identifierinformation, which is sent by a first service controller, of each hop ona second LSP, where the second LSP is an LSP, which is determined by thefirst service controller, from a preset ingress to a preset egress. Thesecond generating module 902 is connected to the second receiving module901 and configured to: identify each hop on the second LSP, according tothe identifier information of each hop on the second LSP, which isreceived by the second receiving module 901, allocate, from second labelspace information of each hop on the second LSP, a label to each hop onthe second LSP, determine incoming and outgoing interface information ofeach hop on the second LSP according to topology information of each hopon the second LSP, and generate forwarding data of each hop on thesecond LSP. The fourth sending module 903 is connected to the secondgenerating module 902 and configured to send the forwarding data of eachhop on the second LSP, which is generated by the second generatingmodule 902, to a node device corresponding to each hop on the second LSPto complete establishment of the second LSP.

In an optional implementation manner of this embodiment, the firstservice controller and the service controller provided by thisembodiment are connected through another network except a first networkto which the first service controller and the service controllerprovided by this embodiment belong. Based on this, the second receivingmodule 901 can be specifically configured to receive, from the firstservice controller, a stitching and binding relationship between thesecond LSP and a fourth LSP, identifier information of each hop that islocated in the first network on the second LSP, and identifierinformation of an ingress of the fourth LSP, where the fourth LSP is anLSP that is established upon triggering by the first service controller,uses the first service controller as the ingress, uses the servicecontroller provided by this embodiment as an egress, and passes throughthe other network. Each hop on the fourth LSP except the ingress and theegress constitutes each hop that is located in the other network on thesecond LSP. The stitching and binding relationship between the secondLSP and the fourth LSP is indication information used to instruct asecond service controller to stitch the second LSP and the fourth LSP.

Based on the foregoing description, the second generating module 902 canbe specifically configured to allocate, from second label spaceinformation of each hop that is located in the first network on thesecond LSP, a label to each hop that is located in the first network onthe second LSP, determine incoming and outgoing interface information ofeach hop that is located in the first network on the second LSPaccording to topology information of each hop that is located in thefirst network on the second LSP, stitch the second LSP and the fourthLSP, and generate forwarding data of each hop that is located in thefirst network and each hop that is located in the other network on thesecond LSP. The second generating module 902 is more specificallyconfigured to allocate an incoming label to the first service controlleron the fourth LSP, where the incoming label is an outgoing label of aprevious hop of the first service controller on the second LSP, andallocate an outgoing label to the service controller provided by thisembodiment on the fourth LSP, where the outgoing label is an incominglabel of a next hop of the service controller provided by thisembodiment on the second LSP. Each hop on the fourth LSP except thefirst service controller and the service controller provided by thisembodiment constitutes each hop that is located in the other network onthe second LSP.

In an optional implementation manner of this embodiment, as shown inFIG. 10, the service controller provided by this embodiment furtherincludes a third receiving module 904. The third receiving module 904 isconfigured to receive registration information sent by each forwardingdevice in a network to which the service controller provided by thisembodiment belongs, where the registration information includes topologyinformation of the forwarding device and second label space informationof the forwarding device. The third receiving module 904 is connected tothe second generating module 902 and configured to provide the topologyinformation of the forwarding device and the second label spaceinformation of the forwarding device for the second generating module902.

In an optional implementation manner of this embodiment, as shown inFIG. 10, the service controller provided by this embodiment furtherincludes a fourth receiving module 905. The fourth receiving module 905is configured to receive identifier information, which is sent by thefirst service controller, of each hop on a first LSP, where the firstLSP is another LSP, which is determined by the first service controller,from the preset ingress to the preset egress, and the first LSP and thesecond LSP have a primary/standby protection relationship.

The foregoing functional modules may be configured to executecorresponding processes in the foregoing method embodiments. Specificworking principles of the functional modules are not described hereinagain and reference may be made to descriptions of the methodembodiments for details.

The service controller provided by this embodiment is used as a secondservice controller and cooperates with a first service controller. Thefirst service controller determines each hop on an LSP from a presetingress to a preset egress. The service controller provided by thisembodiment receives identifier information of each hop on the LSP, whichis provided by the first service controller, allocates a label to eachhop, determines incoming and outgoing interface information of each hop,generates forwarding data of each hop, and then sends the forwardingdata of each hop to a node device corresponding to each hop, so that anode device of each hop on the LSP can forward data according to theforwarding data sent by the service controller provided by thisembodiment and there is no need to periodically send soft state packetssuch as Hello, Path, and Resv between node devices of the hops on theLSP, which alleviates load of the node devices and helps increase thenumber of RSVP-TE LSPs that each node device is capable of supporting.Further, because the service controller provided by this embodimentdetermines each hop on an LSP and calculates forwarding data of each hopin a centralized manner, a user does not need to configure RSVP-TEconfigurations explicitly on each node device, which simplifiescomplexity of user configuration and maintainability and alleviates theuser's configuration burden.

FIG. 11 is a schematic structural diagram of a service controllerprovided by still another embodiment of the present invention. As shownin FIG. 11, the service controller provided by this embodiment includesa receiver 1101, a processor 1102, and a sender 1103.

The receiver 1101 is configured to receive identifier information, whichis sent by a first service controller, of each hop on a second LSP,where the second LSP is an LSP, which is determined by the first servicecontroller, from a preset ingress to a preset egress. The processor 1102is connected to the receiver 1101 and configured to allocate, fromsecond label space information of each hop on the second LSP, a label toeach hop on the second LSP, determine incoming and outgoing interfaceinformation of each hop on the second LSP according to topologyinformation of each hop on the second LSP, and generate forwarding dataof each hop on the second LSP. The sender 1103 is connected to theprocessor 1102 and configured to send the forwarding data of each hop onthe second LSP, which is generated by the processor 1102, to a nodedevice corresponding to each hop on the second LSP to completeestablishment of the second LSP.

In an optional implementation manner of this embodiment, the firstservice controller and the service controller provided by thisembodiment are connected through another network except a first networkto which the first service controller and the service controllerprovided by this embodiment belong. Based on this, the receiver 1101 canbe specifically configured to receive, from the first servicecontroller, a stitching and binding relationship between the second LSPand a fourth LSP, identifier information of each hop that is located inthe first network on the second LSP, and identifier information of aningress of the fourth LSP, where the fourth LSP is an LSP that isestablished upon triggering by the first service controller, uses thefirst service controller as the ingress, uses the service controllerprovided by this embodiment as an egress, and passes through the othernetwork. Each hop on the fourth LSP except the ingress and the egressconstitutes each hop that is located in the other network on the secondLSP. The stitching and binding relationship between the second LSP andthe fourth LSP is indication information used to instruct a secondservice controller to stitch the second LSP and the fourth LSP.

Based on the foregoing description, the processor 1102 can bespecifically configured to allocate, from second label space informationof each hop that is located in the first network on the second LSP, alabel to each hop that is located in the first network on the secondLSP, determine incoming and outgoing interface information of each hopthat is located in the first network on the second LSP according totopology information of each hop that is located in the first network onthe second LSP, stitch the second LSP and the fourth LSP, and generateforwarding data of each hop that is located in the first network andeach hop that is located in the other network on the second LSP.

In an optional implementation manner of this embodiment, the receiver1101 is further configured to receive registration information sent byeach forwarding device in a network to which the service controllerprovided by this embodiment belongs, where the registration informationincludes topology information of the forwarding device and second labelspace information of the forwarding device. The receiver 1101 providesthe topology information of the forwarding device and the second labelspace information of the forwarding device for the processor 1102.

In an optional implementation manner of this embodiment, the receiver1101 is further configured to receive identifier information, which issent by the first service controller, of each hop on a first LSP, wherethe first LSP is another LSP, which is determined by the first servicecontroller, from the preset ingress to the preset egress, and the firstLSP and the second LSP have a primary/standby protection relationship.

The service controller provided by this embodiment may be configured toexecute corresponding processes in the foregoing method embodiments.Specific working principles of the service controller are not describedherein again and reference may be made to descriptions of the methodembodiments for details.

The service controller provided by this embodiment is used as a secondservice controller and cooperates with a first service controller. Thefirst service controller determines each hop on an LSP from a presetingress to a preset egress. The service controller provided by thisembodiment receives identifier information of each hop on the LSP, whichis provided by the first service controller, allocates a label to eachhop, determines incoming and outgoing interface information of each hop,generates forwarding data of each hop, and then sends the forwardingdata of each hop to a node device corresponding to each hop, so that anode device of each hop on the LSP can forward data according to theforwarding data sent by the service controller provided by thisembodiment and there is no need to periodically send soft state packetssuch as Hello, Path, and Resv between node devices of the hops on theLSP, which alleviates load of the node devices and helps increase thenumber of RSVP-TE LSPs that each node device is capable of supporting.Further, because the service controller provided by this embodimentdetermines each hop on an LSP and calculates forwarding data of each hopin a centralized manner, a user does not need to configure RSVP-TEconfigurations explicitly on each node device, which simplifiescomplexity of user configuration and maintainability and alleviates theuser's configuration burden.

FIG. 12 is a schematic structural diagram of a forwarding deviceprovided by an embodiment of the present invention. As shown in FIG. 12,the forwarding device provided by this embodiment includes: a fifthreceiving module 1201 and a fifth sending module 1203.

The fifth receiving module 1201 is configured to receive forwardingdata, which is sent by a service controller, of the forwarding device ona label switching path (LSP) from a preset ingress to a preset egress,where the forwarding data of the forwarding device includes a label thatthe service controller allocates to the forwarding device provided bythe embodiment from label space information of the forwarding deviceprovided by this embodiment, and incoming and outgoing interfaceinformation that the service controller determines for the forwardingdevice provided by this embodiment according to topology information ofthe forwarding device provided by this embodiment. The fifth sendingmodule 1203 is connected to the fifth receiving module 1201 andconfigured to forward data according to the forwarding data of theforwarding device, which is received by the fifth receiving module 1201.

In an optional implementation manner of this embodiment, the servicecontroller includes a first service controller and/or a second servicecontroller; the LSP includes a first LSP and/or a second LSP of two LSPsthat have a primary/standby protection relationship, where each hop onthe first LSP is determined by the first service controller and each hopon the second LSP is determined by the first service controller andprovided for the second service controller; and the label spaceinformation of the forwarding device includes first label spaceinformation and/or a second label space. Based on this, the fifthreceiving module 1201 is specifically configured to receive forwardingdata, which is sent by the first service controller, of the forwardingdevice provided by this embodiment on the first LSP from the presetingress to the preset egress; and/or the fifth receiving module 1201 isspecifically configured to receive forwarding data, which is sent by thesecond service controller, of the forwarding device provided by thisembodiment on the second LSP from the preset ingress to the presetegress.

In an optional implementation manner of this embodiment, as shown inFIG. 12, the forwarding device provided by this embodiment furtherincludes a sixth sending module 1204. The sixth sending module 1204 isconfigured to send first registration information to the first servicecontroller and send second registration information to the secondservice controller, where the first registration information includesthe topology information of the forwarding device provided by thisembodiment and the first label space information of the forwardingdevice provided by this embodiment, and the second registrationinformation includes the topology information of the forwarding deviceprovided by this embodiment and the second label space information ofthe forwarding device provided by this embodiment. Optionally, the sixthsending module 1204 is connected to the fifth receiving module 1201 andconfigured to send, before the fifth receiving module 1201 receives theforwarding data sent by the service controller, registration informationto the service controller.

In an optional implementation manner of this embodiment, the forwardingdevice provided by this embodiment is the preset ingress. In this case,the fifth sending module 1203 can be specifically configured to forwardthe data according to the forwarding data of the forwarding deviceprovided by this embodiment on the first LSP and the forwarding data ofthe forwarding device provided by this embodiment on the second LSP.

Further, the fifth sending module 1203 is more specifically configuredto forward the data according to the forwarding data of the forwardingdevice provided by this embodiment on the first LSP if it is discoveredthat the first service controller is normal, and forward the dataaccording to the forwarding data of the forwarding device provided bythis embodiment on the second LSP if it is discovered that the firstservice controller is faulty.

The foregoing functional modules may be configured to executecorresponding processes in the foregoing method embodiments. Specificworking principles of the functional modules are not described hereinagain and reference may be made to descriptions of the methodembodiments for details.

The forwarding device provided by this embodiment is used as a hop on anLSP from a preset ingress to a preset egress to receive forwarding data,which is sent by a service controller, of the forwarding device on theLSP from the preset ingress to the preset egress and forward dataaccording to the forwarding data, so that there is no need toperiodically send soft state packets, such as Hello, Path, and Resv,between the forwarding device and nodes on the LSP, which alleviatesload of the forwarding device and helps increase the number of RSVP-TELSPs that the forwarding device is capable of supporting.

FIG. 13 is a schematic structural diagram of a forwarding deviceprovided by another embodiment of the present invention. As shown inFIG. 13, the forwarding device provided by this embodiment includes: areceiver 1301 and a sender 1303.

The receiver 1301 is configured to receive forwarding data, which issent by a service controller, of the forwarding device on a labelswitching path (LSP) from a preset ingress to a preset egress, where theforwarding data of the forwarding device includes a label that theservice controller allocates to the forwarding device provided by theembodiment from label space information of the forwarding deviceprovided by this embodiment, and incoming and outgoing interfaceinformation that the service controller determines for the forwardingdevice provided by this embodiment according to topology information ofthe forwarding device provided by this embodiment. The sender 1303 isconnected to the receiver 1301 and configured to forward data accordingto the forwarding data of the forwarding device, which is received bythe receiver 1301.

In an optional implementation manner of this embodiment, the servicecontroller includes a first service controller and/or a second servicecontroller; the LSP includes a first LSP and/or a second LSP of two LSPsthat have a primary/standby protection relationship, where each hop onthe first LSP is determined by the first service controller and each hopon the second LSP is determined by the first service controller andprovided for the second service controller; and the label spaceinformation of the forwarding device includes first label spaceinformation and/or a second label space. Based on this, the receiver1301 is specifically configured to receive forwarding data, which issent by the first service controller, of the forwarding device providedby this embodiment on the first LSP from the preset ingress to thepreset egress; and/or the receiver 1301 is specifically configured toreceive forwarding data, which is sent by the second service controller,of the forwarding device provided by this embodiment on the second LSPfrom the preset ingress to the preset egress.

In an optional implementation manner of this embodiment, the sender 1303is further configured to send first registration information to thefirst service controller and send second registration information to thesecond service controller, where the first registration informationincludes the topology information of the forwarding device provided bythis embodiment and the first label space information of the forwardingdevice provided by this embodiment, and the second registrationinformation includes the topology information of the forwarding deviceprovided by this embodiment and the second label space information ofthe forwarding device provided by this embodiment.

In an optional implementation manner of this embodiment, the forwardingdevice provided by this embodiment is the preset ingress. In this case,the sender 1303 can be specifically configured to forward data accordingto the forwarding data of the forwarding device provided by thisembodiment on the first LSP and the forwarding data of the forwardingdevice provided by this embodiment on the second LSP.

Further, the sender 1303 is more specifically configured to forward thedata according to the forwarding data of the forwarding device providedby this embodiment on the first LSP if it is discovered that the firstservice controller is normal, and forward the data according to theforwarding data of the forwarding device provided by this embodiment onthe second LSP if it is discovered that the first service controller isfaulty.

The forwarding device provided by this embodiment may be configured toexecute corresponding processes in the foregoing method embodiments.Specific working principles of the forwarding device are not describedherein again and reference may be made to descriptions of the methodembodiments for details.

The forwarding device provided by this embodiment is used as a hop on anLSP from a preset ingress to a preset egress to receive forwarding data,which is sent by a service controller, of the forwarding device on theLSP from the preset ingress to the preset egress and forward dataaccording to the forwarding data, so that there is no need toperiodically send soft state packets, such as Hello, Path, and Resv,between the forwarding device and nodes on the LSP, which alleviatesload of the forwarding device and helps increase the number of RSVP-TELSPs that the forwarding device is capable of supporting.

Persons of ordinary skill in the art may understand that all or a partof the steps of the method embodiments may be implemented by a programinstructing relevant hardware. The program may be stored in a computerreadable storage medium. When the program runs, the steps of the methodembodiments are performed. The foregoing storage medium includes: anymedium that can store program code, such as a ROM, a RAM, a magneticdisk, or an optical disk.

Finally, it should be noted that the foregoing embodiments are merelyintended for describing the technical solutions of the present inventionother than limiting the present invention. Although the presentinvention is described in detail with reference to the foregoingembodiments, persons of ordinary skill in the art should understand thatthey may still make modifications to the technical solutions describedin the foregoing embodiments or make equivalent replacements to some orall technical features thereof, without departing from the scope of thetechnical solutions of the embodiments of the present invention.

What is claimed is:
 1. A label switching path (LSP) establishmentmethod, comprising: determining, by a first service controller, each hopon an LSP from a preset ingress to a preset egress; allocating, by thefirst service controller from first label space information of each hop,a label to each hop, determining incoming and outgoing interfaceinformation of each hop according to topology information of each hop,generating forwarding data of each hop, and sending the forwarding dataof each hop to each node device corresponding to each hop to completeestablishment of the LSP; wherein determining, by a first servicecontroller, each hop on an LSP from a preset ingress to a preset egresscomprises: determining, by the first service controller, each hop on afirst LSP and a second LSP that have a primary/standby protectionrelationship and are from the preset ingress to the preset egress;wherein allocating, by the first service controller from first labelspace information of each hop, a label to each hop, determining incomingand outgoing interface information of each hop according to topologyinformation of each hop, generating forwarding data of each hop, andsending the forwarding data of each hop to each node devicecorresponding to each hop to complete establishment of the LSPcomprises: allocating, by the first service controller from first labelspace information of each hop on the first LSP, a label to each hop onthe first LSP, determining incoming and outgoing interface informationof each hop on the first LSP according to topology information of eachhop on the first LSP, generating forwarding data of each hop on thefirst LSP, and then sending the forwarding data of each hop on the firstLSP to each node device corresponding to each hop on the first LSP tocomplete establishment of the first LSP; and sending, by the firstservice controller, identifier information of each hop on the second LSPto a second service controller, so that the second service controllerallocates, from second label space information of each hop on the secondLSP, a label to each hop on the second LSP, determines incoming andoutgoing interface information of each hop on the second LSP accordingto topology information of each hop on the second LSP, generatesforwarding data of each hop on the second LSP, and then sends theforwarding data of each hop on the second LSP to each node devicecorresponding to each hop on the second LSP to complete establishment ofthe second LSP; wherein: the first service controller and the secondservice controller are connected through another network except a firstnetwork to which the first service controller and the second servicecontroller belong; determining, by the first service controller, eachhop on a first LSP from the preset ingress to the preset egresscomprises: determining, by the first service controller, each hop thatis located in the first network on the first LSP from the preset ingressto the preset egress, wherein the first LSP passes through the othernetwork; and allocating, by the first service controller from firstlabel space information of each hop on the first LSP, a label to eachhop on the first LSP, determining incoming and outgoing interfaceinformation of each hop on the first LSP according to topologyinformation of each hop on the first LSP; and generating forwarding dataof each hop on the first LSP comprises: triggering, by the first servicecontroller, establishment of a third LSP, wherein the third LSP is anLSP that uses the first service controller as an ingress, uses thesecond service controller as an egress, and passes through the othernetwork, and allocating, by the first service controller from firstlabel space information of each hop that is located in the first networkon the first LSP, a label to each hop that is located in the firstnetwork on the first LSP, determining incoming and outgoing interfaceinformation of each hop that is located in the first network on thefirst LSP according to topology information of each hop that is locatedin the first network on the first LSP, stitching the first LSP and thethird LSP, and generating forwarding data of each hop that is located inthe first network and each hop that is located in the any other networkon the first LSP.
 2. The LSP establishment method according to claim 1,wherein stitching, by the first service controller, the first LSP andthe third LSP comprises: allocating, by the first service controller, anincoming label to the first service controller on the third LSP, whereinthe incoming label is an outgoing label of a previous hop of the firstservice controller on the first LSP; allocating, by the first servicecontroller, an outgoing label to the second service controller on thethird LSP, wherein the outgoing label is an incoming label of a next hopof the second service controller on the first LSP; and wherein each hopon the third LSP except the first service controller and the secondservice controller constitutes each hop that is located in the othernetwork on the first LSP.
 3. The LSP establishment method according toclaim 1, wherein allocating, by the first service controller from firstlabel space information of each hop, a label to each hop, determiningincoming and outgoing interface information of each hop according totopology information of each hop, generating forwarding data of eachhop, and sending the forwarding data of each hop to each node devicecorresponding to each hop to complete establishment of the LSP furthercomprises: allocating, by the first service controller from first labelspace information of each hop on the second LSP, a label to each hop onthe second LSP, determining incoming and outgoing interface informationof each hop on the second LSP according to topology information of eachhop on the second LSP, generating forwarding data of each hop on thesecond LSP, and then sending the forwarding data of each hop on thesecond LSP to each node device corresponding to each hop on the secondLSP to complete establishment of the second LSP.
 4. The LSPestablishment method according to claim 1, wherein before determining,by a first service controller, each hop on an LSP from a preset ingressto a preset egress, the method comprises: receiving, by the firstservice controller, registration information sent by each forwardingdevice in a network to which the first service controller belongs,wherein the registration information comprises topology information ofeach forwarding device and first label space information of eachforwarding device.
 5. The LSP establishment method according to claim 1,further comprising: sending, by the first service controller, identifierinformation of each hop on the first LSP to the second servicecontroller for backup.
 6. The LSP establishment method according toclaim 1, wherein: the first LSP and the second LSP are bothbidirectional LSPs; or the first LSP and the second LSP are bothunidirectional LSPs.
 7. The LSP establishment method according to claim1, wherein: the first LSP and the second LSP are both point-to-point P2PLSPs; or the first LSP and the second LSP are both point-to-multipointP2MP LSPs.
 8. A label switching path (LSP) establishment method,comprising: receiving, by a second service controller, identifierinformation, which is sent by a first service controller, of each hop ona second LSP, wherein the second LSP is an LSP, which is determined bythe first service controller, from a preset ingress to a preset egress;allocating, by the second service controller from second label spaceinformation of each hop on the second LSP, a label to each hop on thesecond LSP, determining incoming and outgoing interface information ofeach hop on the second LSP according to topology information of each hopon the second LSP, and generating forwarding data of each hop on thesecond LSP; and sending, by the second service controller, theforwarding data of each hop on the second LSP to each node devicecorresponding to each hop on the second LSP to complete establishment ofthe second LSP; the first service controller and the second servicecontroller are connected through another network except a first networkto which the first service controller and the second service controllerbelong; and receiving, by a second service controller, identifierinformation, which is sent by a first service controller, of each hop ona second LSP comprises: receiving, by the second service controller fromthe first service controller, a stitching and binding relationshipbetween the second LSP and a fourth LSP, identifier information of eachhop that is located in the first network on the second LSP, andidentifier information of an ingress of the fourth LSP, wherein thefourth LSP is an LSP that is established upon triggering by the firstservice controller, uses the first service controller as the ingress,uses the second service controller as an egress, and passes through theother network.
 9. The LSP establishment method according to claim 8,wherein allocating, by the second service controller from second labelspace information of each hop on the second LSP, a label to each hop onthe second LSP, determining incoming and outgoing interface informationof each hop on the second LSP according to topology information of eachhop on the second LSP, and generating forwarding data of each hop on thesecond LSP comprises: allocating, by the second service controller fromsecond label space information of each hop that is located in the firstnetwork on the second LSP, a label to each hop that is located in thefirst network on the second LSP, determining incoming and outgoinginterface information of each hop that is located in the first networkon the second LSP according to topology information of each hop that islocated in the first network on the second LSP, stitching the second LSPand the fourth LSP, and generating forwarding data of each hop that islocated in the first network and each hop that is located in the othernetwork on the second LSP.
 10. The LSP establishment method according toclaim 9, wherein stitching, by the second service controller, the secondLSP and the fourth LSP comprises: allocating, by the second servicecontroller, an incoming label to the first service controller on thefourth LSP, wherein the incoming label is an outgoing label of aprevious hop of the first service controller on the second LSP;allocating, by the second service controller, an outgoing label to thesecond service controller on the fourth LSP, wherein the outgoing labelis an incoming label of a next hop of the second service controller onthe second LSP; and wherein each hop on the fourth LSP except the firstservice controller and the second service controller constitutes eachhop that is located in the other network on the second LSP.
 11. The LSPestablishment method according to claim 8, wherein before receiving, bya second service controller, identifier information, which is sent by afirst service controller, of each hop on a second LSP, the methodcomprises: receiving, by the second service controller, registrationinformation sent by each forwarding device in a network to which thesecond service controller belongs, wherein the registration informationcomprises topology information of the each forwarding device and secondlabel space information of the each forwarding device.
 12. The LSPestablishment method according to claim 8, further comprising:receiving, by the second service controller, identifier information,which is sent by the first service controller, of each hop on a firstLSP, wherein the first LSP is another LSP, which is determined by thefirst service controller, from the preset ingress to the preset egress,and the first LSP and the second LSP have a primary/standby protectionrelationship.
 13. A service controller, comprising: a processor,configured to: determine each hop on a first label switching path (LSP)and a second LSP that have a primary/standby protection relationship andare from the preset ingress to the preset egress, and allocate, fromfirst label space information of each hop on the first LSP, a label toeach hop on the first LSP, determine incoming and outgoing interfaceinformation of each hop on the first LSP according to topologyinformation of each hop on the first LSP, and generate forwarding dataof each hop on the first LSP; a sender, configured to: send theforwarding data of each hop on the first LSP to each node devicecorresponding to each hop on the first LSP to complete establishment ofthe first LSP, and send identifier information of each hop on the secondLSP to a second service controller, so that the second servicecontroller allocates, from second label space information of each hop onthe second LSP, a label to each hop on the second LSP, determinesincoming and outgoing interface information of each hop on the secondLSP according to topology information of each hop on the second LSP,generates forwarding data of each hop on the second LSP, and then sendsthe forwarding data of each hop on the second LSP to each node devicecorresponding to each hop on the second LSP to complete establishment ofthe second LSP; the service controller and the second service controllerare connected through another network except a first network to whichthe service controller and the second service controller belong; theprocessor is further configured to: determine each hop that is locatedin the first network on the first LSP from the preset ingress to thepreset egress, wherein the first LSP passes through the other network;trigger establishment of a third LSP, allocate, from first label spaceinformation of each hop that is located in the first network on thefirst LSP, a label to each hop that is located in the first network onthe first LSP, determine incoming and outgoing interface information ofeach hop that is located in the first network on the first LSP accordingto topology information of each hop that is located in the first networkon the first LSP, stitch the first LSP and the third LSP, and generateforwarding data of each hop that is located in the first network andeach hop that is located in the other network on the first LSP, whereinthe third LSP is an LSP that uses the service controller as an ingress,uses the second service controller as an egress, and passes through theother network.
 14. The service controller according to claim 13, whereinthe processor is configured to allocate an incoming label to the servicecontroller on the third LSP, wherein the incoming label is an outgoinglabel of a previous hop of the service controller on the first LSP, andallocate an outgoing label to the second service controller on the thirdLSP, wherein the outgoing label is an incoming label of a next hop ofthe second service controller on the first LSP, wherein each hop on thethird LSP except the service controller and the second servicecontroller constitutes each hop that is located in the other network onthe first LSP.
 15. The service controller according to claim 13,wherein: the processor is configured to: allocate, from first labelspace information of each hop on the second LSP, a label to each hop onthe second LSP, determine incoming and outgoing interface information ofeach hop on the second LSP according to topology information of each hopon the second LSP, and generate forwarding data of each hop on thesecond LSP; and the sender is configured to: send the forwarding data ofeach hop on the second LSP to each node device corresponding to each hopon the second LSP to complete establishment of the second LSP.
 16. Theservice controller according to claim 13, further comprising: areceiver, configured to receive registration information sent by eachforwarding device in a network to which the service controller belongs,wherein the registration information comprises topology information ofeach forwarding device and first label space information of eachforwarding device.
 17. The service controller according to claim 13,wherein: the sender is configured to send identifier information of eachhop on the first LSP to the second service controller for backup.
 18. Aservice controller, comprising: a receiver, configured to receiveidentifier information, which is sent by a first service controller, ofeach hop on a second label switching path (LSP), wherein the second LSPis an LSP, which is determined by the first service controller, from apreset ingress to a preset egress; a processor, configured to allocate,from second label space information of each hop on the second LSP, alabel to each hop on the second LSP, determine incoming and outgoinginterface information of each hop on the second LSP according totopology information of each hop on the second LSP, and generateforwarding data of each hop on the second LSP; a sender, configured tosend the forwarding data of each hop on the second LSP to each nodedevice corresponding to each hop on the second LSP to completeestablishment of the second LSP; the first service controller and theservice controller are connected through another network except a firstnetwork to which the first service controller and the service controllerbelong; and the receiver is configured to receive, from the firstservice controller, a stitching and binding relationship between thesecond LSP and a fourth LSP, identifier information of each hop that islocated in the first network on the second LSP, and identifierinformation of an ingress of the fourth LSP, wherein the fourth LSP isan LSP that is established upon triggering by the first servicecontroller, uses the first service controller as the ingress, uses theservice controller as an egress, and passes through the other network.19. The service controller according to claim 18, wherein the processoris configured to: allocate, from second label space information of eachhop that is located in the first network on the second LSP, a label toeach hop that is located in the first network on the second LSP;determine incoming and outgoing interface information of each hop thatis located in the first network on the second LSP according to topologyinformation of each hop that is located in the first network on thesecond LSP; and stitch the second LSP and the fourth LSP, and generateforwarding data of each hop that is located in the first network andeach hop that is located in the other network on the second LSP.
 20. Theservice controller according to claim 19, wherein the processor isconfigured to: allocate an incoming label to the first servicecontroller on the fourth LSP, wherein the incoming label is an outgoinglabel of a previous hop of the first service controller on the secondLSP; and allocate an outgoing label to the service controller on thefourth LSP, wherein the outgoing label is an incoming label of a nexthop of the service controller on the second LSP, wherein each hop on thefourth LSP except the first service controller and the servicecontroller constitutes each hop that is located in the other network onthe second LSP.
 21. The service controller according to claim 18,wherein the receiver is configured to receive registration informationsent by each forwarding device in a network to which the servicecontroller belongs, wherein the registration information comprisestopology information of each forwarding device and second label spaceinformation of each forwarding device.
 22. The service controlleraccording to claim 18, wherein the receiver is configured to receiveidentifier information, which is sent by the first service controller,of each hop on a first LSP, wherein the first LSP is another LSP, whichis determined by the first service controller, from the preset ingressto the preset egress, and the first LSP and the second LSP have aprimary/standby protection relationship.